Maven Release Plugin Fix
Hi maven-release-plugin committer, There is an issue for the maven-release-plugin (http://jira.codehaus.org/browse/MRELEASE-495) which is prerequisite for the osgi-release-plugin (patch https://issues.sonatype.org/browse/TYCHO-214). Do you plan to take care for that issue? If not now, when do you plan to take care? Regards Matthias
RE: Build parent pom only, skip module build
THX that was what I'm looking for :-) -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Mittwoch, 20. Januar 2010 11:34 To: Maven Users List Subject: Re: Build parent pom only, skip module build The option you are looking for is -N Vach, Matthias wrote: > Hi all, > is there an option to build a parent pom without its childs? > > Example structure: > - > /pom.xml > /mod1/... > /mod2/... > > pom.xml is of packaging-type pom and contains a sections like: > - > > mod1 > mod2 > > > > > I need to build "only" that pom.xml to bring/update it to the local repo. > > Regards Matthias > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Build parent pom only, skip module build
Hi all, is there an option to build a parent pom without its childs? Example structure: - /pom.xml /mod1/... /mod2/... pom.xml is of packaging-type pom and contains a sections like: - mod1 mod2 I need to build "only" that pom.xml to bring/update it to the local repo. Regards Matthias - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: mvn dependency:tree ends up in a nullpointer
Hi does nobody know a solution? Regards Matthias -Ursprüngliche Nachricht- Von: Vach, Matthias [mailto:matthias.v...@sap.com] Gesendet: Donnerstag, 17. September 2009 17:14 An: Maven Users List Betreff: AW: mvn dependency:tree ends up in a nullpointer Upppsss, sorry, I mean: > This is building fine and works as expected but > Sadly the version definition [1.0,) leads to a null pointer when I generate > the dependency:tree (mvn dependency:tree) Regards Matthias -Ursprüngliche Nachricht----- Von: Vach, Matthias [mailto:matthias.v...@sap.com] Gesendet: Donnerstag, 17. September 2009 17:09 An: users@maven.apache.org Betreff: mvn dependency:tree ends up in a nullpointer Hi all, I need to define that any versions of javax.el:el-api are provided by my runtime system and must not be packed into my ear. To avoid excluding that artifact javax.el:el-api from each and every dependency where it is referenced, I defined it as explicit provided artefact: javax.el el-api [1.0,) provided This is building fine and works as expected but Sadly the version definition [1.0,) leads to an null pointer: [ERROR] FATAL ERROR [INFO] [INFO] version was null for javax.el:el-api [INFO] [INFO] Trace java.lang.NullPointerException: version was null for javax.el:el-api at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) at org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) Can you give me the reason for that NPE? THX for your help, Regards Matthias - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: mvn dependency:tree ends up in a nullpointer
Upppsss, sorry, I mean: > This is building fine and works as expected but > Sadly the version definition [1.0,) leads to a null pointer when I generate > the dependency:tree (mvn dependency:tree) Regards Matthias -Ursprüngliche Nachricht----- Von: Vach, Matthias [mailto:matthias.v...@sap.com] Gesendet: Donnerstag, 17. September 2009 17:09 An: users@maven.apache.org Betreff: mvn dependency:tree ends up in a nullpointer Hi all, I need to define that any versions of javax.el:el-api are provided by my runtime system and must not be packed into my ear. To avoid excluding that artifact javax.el:el-api from each and every dependency where it is referenced, I defined it as explicit provided artefact: javax.el el-api [1.0,) provided This is building fine and works as expected but Sadly the version definition [1.0,) leads to an null pointer: [ERROR] FATAL ERROR [INFO] [INFO] version was null for javax.el:el-api [INFO] [INFO] Trace java.lang.NullPointerException: version was null for javax.el:el-api at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) at org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) Can you give me the reason for that NPE? THX for your help, Regards Matthias - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
mvn dependency:tree ends up in a nullpointer
Hi all, I need to define that any versions of javax.el:el-api are provided by my runtime system and must not be packed into my ear. To avoid excluding that artifact javax.el:el-api from each and every dependency where it is referenced, I defined it as explicit provided artefact: javax.el el-api [1.0,) provided This is building fine and works as expected but Sadly the version definition [1.0,) leads to an null pointer: [ERROR] FATAL ERROR [INFO] [INFO] version was null for javax.el:el-api [INFO] [INFO] Trace java.lang.NullPointerException: version was null for javax.el:el-api at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) at org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) Can you give me the reason for that NPE? THX for your help, Regards Matthias
