Xref link generation regression with Maven 3
Hi, when the site reports are created using Maven 3, several of the report plugins don't generate the links to the Source Xref pages, when the JXR Plugin hasn't been executed for that project before. Looking at the code of the affected plugins, You'll see that those plugins first check if the 'xrefLocation' directory already exists. If not, they check if the JXR Plugin is configured for the project - but they won't find any plugin there, because with Maven 3 the report plugins aren't configured in the reporting section of the POM anymore. For Maven 3, the report plugins list for those checks should be retrieved from the Site Plugin configuration instead. Some affected plugins and the Xref link to the 'problematic' code: - Checkstyle Plugin: http://maven.apache.org/plugins/maven-checkstyle-plugin/xref/org/apache/maven/plugin/checkstyle/CheckstyleReport.html#670 - PMD Plugin: http://maven.apache.org/plugins/maven-pmd-plugin/xref/org/apache/maven/plugin/pmd/AbstractPmdReport.html#240 - Surefire Report Plugin: http://maven.apache.org/plugins/maven-surefire-report-plugin/xref/org/apache/maven/plugins/surefire/report/SurefireReportMojo.html#203 As a workaround You could just add a simple JXR Plugin configuration to the reporting section of Your (parent) POM: org.apache.maven.plugins maven-jxr-plugin 2.2 But in my option, the bug (or regression) should be fixed anyway. My only problem is now, that I'm not sure where I should open a JIRA issue for that problem. It seems to affect the report plugins, the Site plugin und maybe even the Maven core. Kind regards Marc - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Tar pom.xml dependencies - Maven Assembly Plugin?
Is the Maven Assembly Plugin the right way for me to define a pom.xml and be able to tar up the jars that are labeled as a dependency? The only way I know how to do this with my limited knowledge is to make the pom.xml a war and allow the war to pull all the dependency jars into the target directory and then tar those up. Thanks for your help, Jay Blanton -- View this message in context: http://maven.40175.n5.nabble.com/Tar-pom-xml-dependencies-Maven-Assembly-Plugin-tp3335797p3335797.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven and esper-4.0.0
It looks like you have defined your source library location incorrectly in your IDE or somewhere in your build. production/esperio-csv/ should not be in the jar and it appears that it is. Ron On 10/01/2011 3:01 PM, Tina Vießmann wrote: Hi, I've got a problem installing esper-4.0.0 using maven. I've got absolutly no idea where it comes from. The output is: [ERROR] Error in manifest for myproject:myesper:jar:0.1-SNAPSHOT : Class in different directory than declared. Path from class name is com/espertech/esperio/AbstractCoordinatedAdapter$1.class but the path in the jar is production/esperio-csv/com/espertech/esperio/AbstractCoordinatedAdapter$1.class from Jar:lib/esper-4.0.0.jar [ERROR] Error in manifest for myproject:myesper:jar:0.1-SNAPSHOT : Class in different directory than declared. Path from class name is com/espertech/esperio/AbstractCoordinatedAdapter.class but the path in the jar isproduction/esperio-csv/com/espertech/esperio/AbstractCoordinatedAdapter.class from Jar:lib/esper-4.0.0.jar [ERROR] Error in manifest for myproject:myesper:jar:0.1-SNAPSHOT : Class in different directory than declared. Path from class name is com/espertech/esperio/AbstractSendableEvent.class but the path in the jar is production/esperio-csv/com/espertech/esperio/AbstractSendableEvent.class from Jar:lib/esper-4.0.0.jar [... and so on ...] Has anyone experienced similar problems? Thank you! :) Tina - 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
Re: maven and esper-4.0.0
On Mon, 10 Jan 2011 21:01:53 +0100, Tina Vießmann wrote: > I've got a problem installing esper-4.0.0 using maven. I've got absolutly > no idea where it comes from. The output is: > > [ERROR] Error in manifest for myproject:myesper:jar:0.1-SNAPSHOT : Class > in different directory than declared. Path from class name is > com/espertech/esperio/AbstractCoordinatedAdapter$1.class but the path in > the jar is > production/esperio-csv/com/espertech/esperio/AbstractCoordinatedAdapter$1.class > from Jar:lib/esper-4.0.0.jar It seems that the esper-4.0.0.jar artifact uploaded to Maven central is broken and contains the "production" path; the jar in the original distribution from Codehaus is OK. Looks like another fine example of a home-grown build script. :( I guess for now you should be able to install the correct jar into your repo/repo manager to override the artifact from central. Please also file a blocker bug in the Esper JIRA (http://jira.codehaus.org/browse/ESPER). -h - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: can i use aggregator as dependency holder?
Your aggregator POM should include all the transitive dependencies unless you excluded them since you are providing them elsewhere (using another POM). The person needs to include a dependency on the aggregated POM and the "elsewhere" POM On 10/01/2011 12:16 PM, Leon Rosenberg wrote: Hi, so I have 4 projects with one aggregator pom and it works just fine for publishing and releasing. I have an aggregator pom, which includes a,b,c,d and it all got built and stuff. Now, if a user of mine wants to use this project, he has to know which of the a,b,c,d modules he actually need, or which is the one, that includes the other. I thought I could save the user the searching and let him just declare the dependency to the aggregator pom, but it obviously don't work (cause maven tries to download the aggregator.jar and not the transitive dependencies). Now for the question, what is the best practice here? Is defining a module with a sounding name, like the-module-you-have-to-include-in-yourpom which is simply a pom, defining dependencies to a,b,c,d and which can be used for transitive resolution, the way to go, or is there another practice? thanks in advance Leon - 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
maven and esper-4.0.0
Hi, I've got a problem installing esper-4.0.0 using maven. I've got absolutly no idea where it comes from. The output is: [ERROR] Error in manifest for myproject:myesper:jar:0.1-SNAPSHOT : Class in different directory than declared. Path from class name is com/espertech/esperio/AbstractCoordinatedAdapter$1.class but the path in the jar is production/esperio-csv/com/espertech/esperio/AbstractCoordinatedAdapter$1.class from Jar:lib/esper-4.0.0.jar [ERROR] Error in manifest for myproject:myesper:jar:0.1-SNAPSHOT : Class in different directory than declared. Path from class name is com/espertech/esperio/AbstractCoordinatedAdapter.class but the path in the jar isproduction/esperio-csv/com/espertech/esperio/AbstractCoordinatedAdapter.class from Jar:lib/esper-4.0.0.jar [ERROR] Error in manifest for myproject:myesper:jar:0.1-SNAPSHOT : Class in different directory than declared. Path from class name is com/espertech/esperio/AbstractSendableEvent.class but the path in the jar is production/esperio-csv/com/espertech/esperio/AbstractSendableEvent.class from Jar:lib/esper-4.0.0.jar [... and so on ...] Has anyone experienced similar problems? Thank you! :) Tina - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: project.getArtifacts() difference between maven 2 and maven 3 in plugin
thanks a lot Benjamin, after setting "@requiresDependencyResolution runitme" it works with maven 2 and maven 3. When using "compile" as an option it didn't work. Greetings, Frank -- View this message in context: http://maven.40175.n5.nabble.com/project-getArtifacts-difference-between-maven-2-and-maven-3-in-plugin-tp3334878p3335168.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
can i use aggregator as dependency holder?
Hi, so I have 4 projects with one aggregator pom and it works just fine for publishing and releasing. I have an aggregator pom, which includes a,b,c,d and it all got built and stuff. Now, if a user of mine wants to use this project, he has to know which of the a,b,c,d modules he actually need, or which is the one, that includes the other. I thought I could save the user the searching and let him just declare the dependency to the aggregator pom, but it obviously don't work (cause maven tries to download the aggregator.jar and not the transitive dependencies). Now for the question, what is the best practice here? Is defining a module with a sounding name, like the-module-you-have-to-include-in-yourpom which is simply a pom, defining dependencies to a,b,c,d and which can be used for transitive resolution, the way to go, or is there another practice? thanks in advance Leon - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: project.getArtifacts() difference between maven 2 and maven 3 in plugin
fmeili wrote:
My plugin needs all dependend artifacts (includeing transitives) of the
project. With maven 2.2.1 the call to project.getArtifacts() works correct.
When using it with maven 3.0.1 the returned set of artifacts for a project
has a size of zero.
Code snippets:
/**
* @goal myGoal
* @phase package
* @inheritByDefault false
* @threadSafe
*/
public class MyEar extends AbstractMojo {
...
/**
* @parameter default-value="${project}"
* @required
* @readonly
*/
protected MavenProject project;
...
Set artifacts = project.getArtifacts(); // set is empty in maven 3 but ok in
maven 2
I played with the javadoc class annotation "@requiresDependencyResolution
You need this annotation, whether you request compile, runtime or test
classpath is a choice you need to make.
Plugins accessing dependencies without this annotation produce random
results in Maven 2 depending on which plugins ran before.
Benjamin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: New test folder are not recognized in eclipse
ah sorry my fault... this should be sent to the m2eclipse list -- View this message in context: http://maven.40175.n5.nabble.com/New-test-folder-are-not-recognized-in-eclipse-tp3334855p3334866.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
project.getArtifacts() difference between maven 2 and maven 3 in plugin
Hi,
I've some problems while migrating my projects and plugins from maven 2.2.1
to maven 3.0.1. My self developed plugin does not longer work with maven 3.
My plugin needs all dependend artifacts (includeing transitives) of the
project. With maven 2.2.1 the call to project.getArtifacts() works correct.
When using it with maven 3.0.1 the returned set of artifacts for a project
has a size of zero.
Code snippets:
/**
* @goal myGoal
* @phase package
* @inheritByDefault false
* @threadSafe
*/
public class MyEar extends AbstractMojo {
...
/**
* @parameter default-value="${project}"
* @required
* @readonly
*/
protected MavenProject project;
...
Set artifacts = project.getArtifacts(); // set is empty in maven 3 but ok in
maven 2
I played with the javadoc class annotation "@requiresDependencyResolution
compile" but this produce wrong results for maven 2 and also didn't change
anything for maven 3, it's still an empty set.
Has someone an idea what's wrong with my code?
Thanks in advance,
Frank
--
View this message in context:
http://maven.40175.n5.nabble.com/project-getArtifacts-difference-between-maven-2-and-maven-3-in-plugin-tp3334878p3334878.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: New test folder are not recognized in eclipse
I think you'll get a much much better answer on the m2eclipse mailing list. You say "on every change". Is that true, isn't it only when a new source folder is added. Which should happen too often. /Anders On Mon, Jan 10, 2011 at 14:58, MartyMcFly wrote: > > HI, > > we use Eclipse 3.6 with m2eclipse 0.10.2 and Maven 2. When in a project > someone adds as new folder "src/test/java" it is automatically recognized > as > source folder and works. > > If someone else checks the the changed structure from SVN the folder is > retrieved, but Eclipse/m2Eclipse does not recognize it as a source folder > and its missing from the Java Developer View. It is there as one can see it > in the Navigator view. > > The workaround is to call "Maven->Update Project Configuration" on the > project and then the source folder is recognize. > > Is there a better way ? Because running it manually on every change is > quite > hard. > > Thanks or any hint > -- > View this message in context: > http://maven.40175.n5.nabble.com/New-test-folder-are-not-recognized-in-eclipse-tp3334855p3334855.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: project for libraries
On 10/01/2011 4:46 AM, Thomas Sundberg wrote: On Sun, Jan 9, 2011 at 16:27, Ron Wheeler wrote: I am not sure what the big difference is but I imagine Intellij must have some very good features that makes it worth paying for a product. Intellij IDEA is available as open source and therefore doesn't cost you anything. I did not see that on their site. I thought that I saw that it is free for those developing open source project but otherwise must be licensed at some cost. The major difference is in my opinion that it just works without hassle. My experience with Eclipse is that it doesn't work as good. It was certainly hard to install and get set up with all the required plug-ins. That is why I recommend the STS version from Springsource. It comes already loaded with all of the plug-ins required (except the Subversion connectors) to develop with Maven et al. It specifically includes a reasonable current version of M2 from Sonatype. We used the eclipse.org distribution for 2 years before switching to STS. I'm probably biased, I have used Eclipse for a quite short period of time and Idea close to 10 years now. IDEA has been mentioned here and in other forums as a good tool. I assume that it has a good set of graphical tools for Maven. /Thomas, not really interested in starting a flame war... :) Me neither but I certainly would recommend that anyone still using Eclipse and Maven to try the STS version. Anyone who does not have a good IDE with Maven support should look at Eclipse/STS or IDEA. Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
New test folder are not recognized in eclipse
HI, we use Eclipse 3.6 with m2eclipse 0.10.2 and Maven 2. When in a project someone adds as new folder "src/test/java" it is automatically recognized as source folder and works. If someone else checks the the changed structure from SVN the folder is retrieved, but Eclipse/m2Eclipse does not recognize it as a source folder and its missing from the Java Developer View. It is there as one can see it in the Navigator view. The workaround is to call "Maven->Update Project Configuration" on the project and then the source folder is recognize. Is there a better way ? Because running it manually on every change is quite hard. Thanks or any hint -- View this message in context: http://maven.40175.n5.nabble.com/New-test-folder-are-not-recognized-in-eclipse-tp3334855p3334855.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: release:prepare fails to tag a ClearCase view
I browsed through the source code and it seems it takes the project "basedir" and use it as the folder to label -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: ב 10 ינואר 2011 14:57 To: Maven Users List Subject: Re: release:prepare fails to tag a ClearCase view I haven't really investigated any alterantive, but that's what I do. It's pain though, and sooner or later I'll look into if it can be automated. However, as it currently isn't I'm guessing it might not be possible. /Anders 2011/1/10 Perez Ronen > release:prepare does not fail. release:perform fails due to wrong label. > > Your suggestion to manually set label worked - thanks. I guess this is the > only way to achieve the release:perform. > > Thanks, > Ronen. > > -Original Message- > From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On > Behalf Of Anders Hammar > Sent: ב 10 ינואר 2011 14:01 > To: Maven Users List > Subject: Re: release:prepare fails to tag a ClearCase view > > I don't understand. Does release:prepare fail? Or isn't it just doing what > you want? > If it fails, please provide the error message. > > My experience with m-release-p and ClearCase is that I manually need to put > the label on the folder above my project (all the way to the root) after I > perform release:prepare. Then I can execute release:perform. > > /Anders > > On Mon, Jan 10, 2011 at 12:08, Perez Ronen > wrote: > > > Hi All, > > > > > > > > I am trying to setup a release to a Maven project with release:prepare > and > > release:perform. > > > > My project layout is something like: > > > > > > > > /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj/pom.xml > > > > > > > > When running the release prepare, one of the things needed to be done is > > put a label (tag) on this view, in order to later create a new view based > on > > the current view for the next release. > > > > The following is a line from the release:prepare output: > > > > > > > > [DEBUG] Executing: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj > > >>/bin/sh -c cd /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj && > > cleartool mklbtype -nc new-label > > > > [DEBUG] Executing: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj > > >>/bin/sh -c cd /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj && > > cleartool mklabel -recurse new-label . > > > > > > > > > > > > The problem is that the label is set for the root tree of my-proj as a > > result of the "cd" command. I would like the cd to change dir to > > /VIEW-NAME/VOB-NAME to tag from parent-dir down. This later fails the > > performing of the release. > > > > > > > > Any idea on how to set a different base directory to tag? > > > > > > > > Thanks, > > > > > > > > Ronen. > > > > > > > > Ronen Perez > > Chief Programming Office > > Comverse > > Office: +972 3 7655701 > > Mobile: +972 52 8545701 > > ronen.pe...@comverse.commailto:ronen.pe...@comverse.com> > > www.comverse.comhttp://www.comverse.com/> > > > > > > > > "This e-mail message may contain confidential, commercial or privileged > > information that constitutes proprietary information of Comverse > Technology > > or its subsidiaries. If you are not the intended recipient of this > message, > > you are hereby notified that any review, use or distribution of this > > information is absolutely prohibited and we request that you delete all > > copies and contact us by e-mailing to: secur...@comverse.com. Thank > You." > > > > “This e-mail message may contain confidential, commercial or privileged > information that constitutes proprietary information of Comverse Technology > or its subsidiaries. If you are not the intended recipient of this message, > you are hereby notified that any review, use or distribution of this > information is absolutely prohibited and we request that you delete all > copies and contact us by e-mailing to: secur...@comverse.com. Thank You.” > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > “This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You.”
Re: release:prepare fails to tag a ClearCase view
I haven't really investigated any alterantive, but that's what I do. It's pain though, and sooner or later I'll look into if it can be automated. However, as it currently isn't I'm guessing it might not be possible. /Anders 2011/1/10 Perez Ronen > release:prepare does not fail. release:perform fails due to wrong label. > > Your suggestion to manually set label worked - thanks. I guess this is the > only way to achieve the release:perform. > > Thanks, > Ronen. > > -Original Message- > From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On > Behalf Of Anders Hammar > Sent: ב 10 ינואר 2011 14:01 > To: Maven Users List > Subject: Re: release:prepare fails to tag a ClearCase view > > I don't understand. Does release:prepare fail? Or isn't it just doing what > you want? > If it fails, please provide the error message. > > My experience with m-release-p and ClearCase is that I manually need to put > the label on the folder above my project (all the way to the root) after I > perform release:prepare. Then I can execute release:perform. > > /Anders > > On Mon, Jan 10, 2011 at 12:08, Perez Ronen > wrote: > > > Hi All, > > > > > > > > I am trying to setup a release to a Maven project with release:prepare > and > > release:perform. > > > > My project layout is something like: > > > > > > > > /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj/pom.xml > > > > > > > > When running the release prepare, one of the things needed to be done is > > put a label (tag) on this view, in order to later create a new view based > on > > the current view for the next release. > > > > The following is a line from the release:prepare output: > > > > > > > > [DEBUG] Executing: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj > > >>/bin/sh -c cd /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj && > > cleartool mklbtype -nc new-label > > > > [DEBUG] Executing: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj > > >>/bin/sh -c cd /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj && > > cleartool mklabel -recurse new-label . > > > > > > > > > > > > The problem is that the label is set for the root tree of my-proj as a > > result of the "cd" command. I would like the cd to change dir to > > /VIEW-NAME/VOB-NAME to tag from parent-dir down. This later fails the > > performing of the release. > > > > > > > > Any idea on how to set a different base directory to tag? > > > > > > > > Thanks, > > > > > > > > Ronen. > > > > > > > > Ronen Perez > > Chief Programming Office > > Comverse > > Office: +972 3 7655701 > > Mobile: +972 52 8545701 > > ronen.pe...@comverse.commailto:ronen.pe...@comverse.com> > > www.comverse.comhttp://www.comverse.com/> > > > > > > > > "This e-mail message may contain confidential, commercial or privileged > > information that constitutes proprietary information of Comverse > Technology > > or its subsidiaries. If you are not the intended recipient of this > message, > > you are hereby notified that any review, use or distribution of this > > information is absolutely prohibited and we request that you delete all > > copies and contact us by e-mailing to: secur...@comverse.com. Thank > You." > > > > “This e-mail message may contain confidential, commercial or privileged > information that constitutes proprietary information of Comverse Technology > or its subsidiaries. If you are not the intended recipient of this message, > you are hereby notified that any review, use or distribution of this > information is absolutely prohibited and we request that you delete all > copies and contact us by e-mailing to: secur...@comverse.com. Thank You.” > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
build assemblies with overlapping resources
i stumbled across the problem, that assembly-plugin can't handle overlapping
resources very well. in my case i tried to build an project depending on
emf(wiki.eclipse.org/index.php/EMF-FAQ#How_d..._ordinary_main.29.3F)
the problem is, each jar-File includes a "plugin.properties"-file which will
be overwritten by assembly plugin.
googling around yields "one-jar-plugin is what you need" but this isn't
working either. in fact it yields the same error - a missing resource
("_UI_DiagnosticRoot_diagnostic = Diagnosis of {0}"). the only difference
is, building it with assembly this resource is really missing (the jar only
has one plugin.properties without "_UI_DiagnosticRoot_diagnostic"). building
it with one-jar, i got a jar including all needed jars but it seems they are
not resolved correctly.
so how to get it working with one-jar. or how to get a clue why it is not
working?
(at the moment i use shade-plugin to solve this problem, this is working -
it simply merges all plugin.properties in one big file. but i can't ensure
that mering property files don't overwrites resources within this files)
--
View this message in context:
http://maven.40175.n5.nabble.com/build-assemblies-with-overlapping-resources-tp3334759p3334759.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: release:prepare fails to tag a ClearCase view
release:prepare does not fail. release:perform fails due to wrong label. Your suggestion to manually set label worked - thanks. I guess this is the only way to achieve the release:perform. Thanks, Ronen. -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: ב 10 ינואר 2011 14:01 To: Maven Users List Subject: Re: release:prepare fails to tag a ClearCase view I don't understand. Does release:prepare fail? Or isn't it just doing what you want? If it fails, please provide the error message. My experience with m-release-p and ClearCase is that I manually need to put the label on the folder above my project (all the way to the root) after I perform release:prepare. Then I can execute release:perform. /Anders On Mon, Jan 10, 2011 at 12:08, Perez Ronen wrote: > Hi All, > > > > I am trying to setup a release to a Maven project with release:prepare and > release:perform. > > My project layout is something like: > > > > /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj/pom.xml > > > > When running the release prepare, one of the things needed to be done is > put a label (tag) on this view, in order to later create a new view based on > the current view for the next release. > > The following is a line from the release:prepare output: > > > > [DEBUG] Executing: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj > >>/bin/sh -c cd /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj && > cleartool mklbtype -nc new-label > > [DEBUG] Executing: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj > >>/bin/sh -c cd /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj && > cleartool mklabel -recurse new-label . > > > > > > The problem is that the label is set for the root tree of my-proj as a > result of the "cd" command. I would like the cd to change dir to > /VIEW-NAME/VOB-NAME to tag from parent-dir down. This later fails the > performing of the release. > > > > Any idea on how to set a different base directory to tag? > > > > Thanks, > > > > Ronen. > > > > Ronen Perez > Chief Programming Office > Comverse > Office: +972 3 7655701 > Mobile: +972 52 8545701 > ronen.pe...@comverse.commailto:ronen.pe...@comverse.com> > www.comverse.comhttp://www.comverse.com/> > > > > "This e-mail message may contain confidential, commercial or privileged > information that constitutes proprietary information of Comverse Technology > or its subsidiaries. If you are not the intended recipient of this message, > you are hereby notified that any review, use or distribution of this > information is absolutely prohibited and we request that you delete all > copies and contact us by e-mailing to: secur...@comverse.com. Thank You." > “This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You.” - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release:prepare fails to tag a ClearCase view
I don't understand. Does release:prepare fail? Or isn't it just doing what you want? If it fails, please provide the error message. My experience with m-release-p and ClearCase is that I manually need to put the label on the folder above my project (all the way to the root) after I perform release:prepare. Then I can execute release:perform. /Anders On Mon, Jan 10, 2011 at 12:08, Perez Ronen wrote: > Hi All, > > > > I am trying to setup a release to a Maven project with release:prepare and > release:perform. > > My project layout is something like: > > > > /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj/pom.xml > > > > When running the release prepare, one of the things needed to be done is > put a label (tag) on this view, in order to later create a new view based on > the current view for the next release. > > The following is a line from the release:prepare output: > > > > [DEBUG] Executing: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj > >>/bin/sh -c cd /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj && > cleartool mklbtype -nc new-label > > [DEBUG] Executing: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj > >>/bin/sh -c cd /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj && > cleartool mklabel -recurse new-label . > > > > > > The problem is that the label is set for the root tree of my-proj as a > result of the "cd" command. I would like the cd to change dir to > /VIEW-NAME/VOB-NAME to tag from parent-dir down. This later fails the > performing of the release. > > > > Any idea on how to set a different base directory to tag? > > > > Thanks, > > > > Ronen. > > > > Ronen Perez > Chief Programming Office > Comverse > Office: +972 3 7655701 > Mobile: +972 52 8545701 > ronen.pe...@comverse.commailto:ronen.pe...@comverse.com> > www.comverse.comhttp://www.comverse.com/> > > > > "This e-mail message may contain confidential, commercial or privileged > information that constitutes proprietary information of Comverse Technology > or its subsidiaries. If you are not the intended recipient of this message, > you are hereby notified that any review, use or distribution of this > information is absolutely prohibited and we request that you delete all > copies and contact us by e-mailing to: secur...@comverse.com. Thank You." >
release:prepare fails to tag a ClearCase view
Hi All, I am trying to setup a release to a Maven project with release:prepare and release:perform. My project layout is something like: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj/pom.xml When running the release prepare, one of the things needed to be done is put a label (tag) on this view, in order to later create a new view based on the current view for the next release. The following is a line from the release:prepare output: [DEBUG] Executing: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj >>/bin/sh -c cd /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj && cleartool mklbtype -nc new-label [DEBUG] Executing: /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj >>/bin/sh -c cd /VIEW-NAME/VOB-NAME/parent-dir/workspace/my-proj && cleartool mklabel -recurse new-label . The problem is that the label is set for the root tree of my-proj as a result of the "cd" command. I would like the cd to change dir to /VIEW-NAME/VOB-NAME to tag from parent-dir down. This later fails the performing of the release. Any idea on how to set a different base directory to tag? Thanks, Ronen. Ronen Perez Chief Programming Office Comverse Office: +972 3 7655701 Mobile: +972 52 8545701 ronen.pe...@comverse.commailto:ronen.pe...@comverse.com> www.comverse.comhttp://www.comverse.com/> "This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You."
Re: project for libraries
On Sun, Jan 9, 2011 at 16:27, Ron Wheeler wrote: > I am not sure what the big difference is but I imagine Intellij must have > some very good features that makes it worth paying for a product. Intellij IDEA is available as open source and therefore doesn't cost you anything. The major difference is in my opinion that it just works without hassle. My experience with Eclipse is that it doesn't work as good. I'm probably biased, I have used Eclipse for a quite short period of time and Idea close to 10 years now. /Thomas, not really interested in starting a flame war... :) -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ Twitter: @thomassundberg Better software through faster feedback - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
