I just grabbed the latest source from CVS and tried to build using mvn create install, but I got errors because it couldn't find the project's parent, net.modularity/modularity-parent, in the standard repositories. I worked around this by adding the modularity-releases repository from http://wiki.modularity.net.au/ical4j/index.php?title=Maven2 to pom.xml. The only problem I have with this is that now I get a lot of bogus warnings because it looks at the new repository first for ALL of the dependencies, and most of them aren't there. Is there a better solution?
Thanks,
hankg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think probably the best approach is to define the repository under the profiles configuration in your settings.xml. I've just updated the Wiki to explain how to do this:
Note that to ensure maven doesn't try to find all your other dependencies in the Modularity repository the profile containing the modularity-releases repository should not be active by default (i.e. don't specify it in the activeProfiles configuration). When you want to update the iCal4j dependency (which you only need to do once for each release), you would explicitly enable the relevant profile. e.g:
% mvn compile -P modularity-releases
I realise this is still not ideal, but hopefully I'll get the release into the master repository soon. :)
regards,
ben
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The error : [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM).
I just grabbed the latest source from CVS and tried to build using mvn create install, but I got errors because it couldn't find the project's parent, net.modularity/modularity-parent, in the standard repositories. I worked around this by adding the modularity-releases repository from http://wiki.modularity.net.au/ical4j/index.php?title=Maven2 to pom.xml. The only problem I have with this is that now I get a lot of bogus warnings because it looks at the new repository first for ALL of the dependencies, and most of them aren't there. Is there a better solution?
Thanks,
hankg
I think probably the best approach is to define the repository under the profiles configuration in your settings.xml. I've just updated the Wiki to explain how to do this:
http://wiki.modularity.net.au/ical4j/index.php?title=Maven2
Note that to ensure maven doesn't try to find all your other dependencies in the Modularity repository the profile containing the modularity-releases repository should not be active by default (i.e. don't specify it in the activeProfiles configuration). When you want to update the iCal4j dependency (which you only need to do once for each release), you would explicitly enable the relevant profile. e.g:
% mvn compile -P modularity-releases
I realise this is still not ideal, but hopefully I'll get the release into the master repository soon. :)
regards,
ben
Thanks.
hankg
Hi iCal4j Team,
i'm using iCal4j on my project. I have a error on the build using maven.
I had the dependancy on my pom file :
The error :
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: net.fortuna.ical4j:ical4j:bundle:1.0-rc3
Reason: Cannot find parent: net.modularity:modularity-parent for project: net.fortuna.ical4j:ical4j:bundle:1.0-rc3 for project net.fortuna.ical4j:ical4j:bundle:1.0-rc3
I can't access to the wiki : http://wiki.modularity.net.au/ical4j/index.php?title=Maven2
server not find !
Can you help please !
Thanks
++