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
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: Shade plugin on Multimodule projects
thanks its working now :) one question to add. Is there a simple configuration to exclude transitive dependencies ? for now I only found to explicitly define the direct dependencies in the include section of artifactSet, but with that you have to maintain the dependencies twice. Thanks -- View this message in context: http://maven.40175.n5.nabble.com/Shade-plugin-on-Multimodule-projects-tp511665p511671.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
Shade plugin on Multimodule projects
Hi, I have a multimodule project for which I want to use the shade plugin. All is configured in the parent pom. Running on the parent with "mvn clean package" fails with Replacing null with d:\workspace-maven\assemblies\parent\target\parent-0.0.1-SNAPSHOT-shaded.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating shaded jar: null so how do I need to configure the plugin to not shade the parent as its not a jar but a pom ? Thanks Marty -- View this message in context: http://maven.40175.n5.nabble.com/Shade-plugin-on-Multimodule-projects-tp511665p511665.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
Exludes in assembly
Hi all,
I want to create an assembly with the assembly plugin, but exclude files -
which I fail.
I use:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
openjet-jars
jar
false
true
runtime
${project.build.outputDirectory}
**/*.exe
but still I do get some exe files in the final jar.
How do I configure the plugin correctly to avoid special files included ?
Thanks
Marty
--
View this message in context:
http://maven.40175.n5.nabble.com/Exludes-in-assembly-tp510622p510622.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: Activate differernt profiles in Multimodule projects
This is actually a nice idea... thanks - going for this Tim Kettler wrote: > > Hi, > > wouldn't adding a specialized parent pom for modules containing idl > files to your project work? > > -Tim > > On 04.06.2010 10:33, MartyMcFly wrote: >> >> thanks for the answer. >> >> Sorry I probably should have add more information. >> >> It is generated source code. We have IDL files for Corba which are in >> project folder 'idl' - but not all modules have this idl folder. >> >> The idea is: in case of a 'idl' folder, the system to generate the java >> files from idl files is running and the /target/generated-sources (in >> which >> the java files are generated) is added as source folder. >> >> if no idl folder is given, the "normal" way to should proceed. >> >> But the problem remains that this system for the idls should only be >> active >> when this idl folder is present - is this possible to define in the >> parent >> pom ? (especially as the idl2java system requires addtional dependencies >> etc >> - I dont want to redefine that in every pom of a module which requires >> it). >> >> As we are bound to visibroker and there is no maven plugin available, we >> are >> required to find another solution :( >> >> >> Stephen Connolly-2 wrote: >>> >>> On 4 June 2010 09:18, MartyMcFly wrote: >>> >>>> >>>> Hi, >>>> >>>> I have a multimodule project in which some modules need an additional >>>> sourcefolder, whereas other modules dont. >>>> To avoid redefining this in each of the relevant modules I want to add >>>> this >>>> to the parent pom and activate the project if this folder X is present. >>>> >>>> Unfortunately this seems not working as the activation section seems to >>>> be >>>> interpreted during the parent pom, where no folder X exists. Ergo the >>>> profile is deactivated and the relevant modules are failing. >>>> >>>> How can I activate profiles, defined in the parent pom, for some >>>> modules >>>> ? >>>> >>>> Is there another way which avoids redefining this in every module ? >>>> >>> >>> don't go against the maven way... apart from generated source code, you >>> should only have one source folder per module... and if you are >>> generating >>> source code, best practice is to keep that in its own module (but >>> obviously >>> generate the source code into target/generated-source/plugin-name/. >>> and >>> have the plugin add the generated directory as a source root... only as >>> a >>> last resource should you use build-helper) >>> >>> >>>> >>>> Thanks >>>> >>>> PS: Using maven 2.2.1 >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28776973.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 >>>> >>>> >>> >>> >> > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28777874.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: Activate differernt profiles in Multimodule projects
thanks for the answer. Sorry I probably should have add more information. It is generated source code. We have IDL files for Corba which are in project folder 'idl' - but not all modules have this idl folder. The idea is: in case of a 'idl' folder, the system to generate the java files from idl files is running and the /target/generated-sources (in which the java files are generated) is added as source folder. if no idl folder is given, the "normal" way to should proceed. But the problem remains that this system for the idls should only be active when this idl folder is present - is this possible to define in the parent pom ? (especially as the idl2java system requires addtional dependencies etc - I dont want to redefine that in every pom of a module which requires it). As we are bound to visibroker and there is no maven plugin available, we are required to find another solution :( Stephen Connolly-2 wrote: > > On 4 June 2010 09:18, MartyMcFly wrote: > >> >> Hi, >> >> I have a multimodule project in which some modules need an additional >> sourcefolder, whereas other modules dont. >> To avoid redefining this in each of the relevant modules I want to add >> this >> to the parent pom and activate the project if this folder X is present. >> >> Unfortunately this seems not working as the activation section seems to >> be >> interpreted during the parent pom, where no folder X exists. Ergo the >> profile is deactivated and the relevant modules are failing. >> >> How can I activate profiles, defined in the parent pom, for some modules >> ? >> >> Is there another way which avoids redefining this in every module ? >> > > don't go against the maven way... apart from generated source code, you > should only have one source folder per module... and if you are generating > source code, best practice is to keep that in its own module (but > obviously > generate the source code into target/generated-source/plugin-name/. > and > have the plugin add the generated directory as a source root... only as a > last resource should you use build-helper) > > >> >> Thanks >> >> PS: Using maven 2.2.1 >> -- >> View this message in context: >> http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28776973.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 >> >> > > -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28777178.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
Activate differernt profiles in Multimodule projects
Hi, I have a multimodule project in which some modules need an additional sourcefolder, whereas other modules dont. To avoid redefining this in each of the relevant modules I want to add this to the parent pom and activate the project if this folder X is present. Unfortunately this seems not working as the activation section seems to be interpreted during the parent pom, where no folder X exists. Ergo the profile is deactivated and the relevant modules are failing. How can I activate profiles, defined in the parent pom, for some modules ? Is there another way which avoids redefining this in every module ? Thanks PS: Using maven 2.2.1 -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28776973.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: POM as dependency fails
its solved... it was a configuration issue on our side. everything works now :) MartyMcFly wrote: > > Hi all, > > I have Project-A which defines a bunch of libraries (jar) for testing > (scope compile) with packaging set to pom. This pom is available at our > repository. > > Project-B now defines Project-A's pom as dependency ( i found that in the > maven sonatype book as an advice) (scope test). > > All libs are at the remote and the locale repository. > > Nevertheless when I type "mvn test" at the console it fails because it > cant resolve (e.g) junit which is defined in Project-A (which pom > Project-B has). > > Funnily Project-A also has a dependency to Project-C's pom (scope compile) > ... and the libs which are in that pom are resolved successfully (running > "mvn compile" resolves it and builds successfully) > > Can someone somehow explain why and what might go wrong here ? > > Thanks for any support > -- View this message in context: http://old.nabble.com/POM-as-dependency-fails-tp28690145p28690903.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
POM as dependency fails
Hi all, I have Project-A which defines a bunch of libraries (jar) for testing (scope compile) with packaging set to pom. This pom is available at our repository. Project-B now defines Project-A's pom as dependency ( i found that in the maven sonatype book as an advice) (scope test). All libs are at the remote and the locale repository. Nevertheless when I type "mvn test" at the console it fails because it cant resolve (e.g) junit which is defined in Project-A (which pom Project-B has). Funnily Project-A also has a dependency to Project-C's pom (scope compile) ... and the libs which are in that pom are resolved successfully (running "mvn compile" resolves it and builds successfully) Can someone somehow explain why and what might go wrong here ? Thanks for any support -- View this message in context: http://old.nabble.com/POM-as-dependency-fails-tp28690145p28690145.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:test with Junit4
thanks to all your answers. Anders Hammar wrote: > > Also, when using JUnit 4, your test class should NOT extend from any JUnit > class as was the case in JUnit 3. I remember a very tricky issue on this > mailing list a year or so ago, where someone used JUnit 4 style > annotations > but the tests weren't run. The reason was that the test class extended > JUnit > 3's TestCase class. > As Junit 4 is backwards compatible, it would compile. But it wouldn't run > with the surefire plugin in Maven. > > /Anders > > On Wed, May 26, 2010 at 14:50, Nicola Musatti > wrote: > >> Specifying a dependency to junit-4.8.1.jar with test scope works for me, >> as >> in: >> >> >> junit >> junit >> 4.8.1 >> test >> >> >> Cheers, >> Nicola Musatti >> >> >> MartyMcFly wrote: >> >>> Hi, >>> >>> I do have problems running Junit4 Tests with Maven surefire. >>> >>> Apparently it only recognizes JUnit3 testcases. So @Test or @Before >>> annotated methods are ignored. Only if they follow the Junit3 style they >>> are >>> run. >>> >>> I have junit-dep.4.7.jar as dependencies, the tests are in src/test/java >>> and >>> running in Eclipse via "Run As" -> "Junit Tests" work fine. >>> >>> The surefire plugin is version 2.4.3 >>> >>> Is there any way to tell surefire to run with Junit 4 ? >>> >>> Thanks >>> >>> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > -- View this message in context: http://old.nabble.com/Maven%3Atest-with-Junit4-tp28679295p28690094.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:test with Junit4
ok.. I found http://old.nabble.com/JUnit-4-%40Before-ts13911963.html#a13912218 that junit-dep does not trigger the JUnit4 Runner in surefire. But as this is over 2 years old now - I'm wondering whether und why this is still doing so ?! MartyMcFly wrote: > > Hi, > > I do have problems running Junit4 Tests with Maven surefire. > > Apparently it only recognizes JUnit3 testcases. So @Test or @Before > annotated methods are ignored. Only if they follow the Junit3 style they > are run. > > I have junit-dep.4.7.jar as dependencies, the tests are in src/test/java > and running in Eclipse via "Run As" -> "Junit Tests" work fine. > > The surefire plugin is version 2.4.3 > > Is there any way to tell surefire to run with Junit 4 ? > > Thanks > -- View this message in context: http://old.nabble.com/Maven%3Atest-with-Junit4-tp28679295p28679322.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
Maven:test with Junit4
Hi, I do have problems running Junit4 Tests with Maven surefire. Apparently it only recognizes JUnit3 testcases. So @Test or @Before annotated methods are ignored. Only if they follow the Junit3 style they are run. I have junit-dep.4.7.jar as dependencies, the tests are in src/test/java and running in Eclipse via "Run As" -> "Junit Tests" work fine. The surefire plugin is version 2.4.3 Is there any way to tell surefire to run with Junit 4 ? Thanks -- View this message in context: http://old.nabble.com/Maven%3Atest-with-Junit4-tp28679295p28679295.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: Migration to Maven ?!
Thanks for the answer. the site functionality problem wouldnt be any concern right now. Can you say something about maven3-beta-1 and Hudson ? This would be more important for us. In Hudson I can currently only set up a Maven2 project - is this also working with Maven 3 oder do we have to wait till the maven plugin in hudson is updated ? Thanks Anders Hammar wrote: > > I suggest using Maven 3.0-beta-1 right now. It is very stable and lots of > existing bugs in 2.2.1 have been fixed. However, be aware that there is > currently some incompatibilities with the site functionality > (maven-site-plugin). > > regarding b), I could point out that m2eclipse is already using Maven 3 > (the > alpha/beta). > > /Anders > > On Fri, May 7, 2010 at 13:35, MartyMcFly wrote: > >> >> Hello all, >> >> I need some helpful information and hope to find it here :-) >> >> In our company we consider to move from our current horrible build >> structure >> to Maven. >> >> With seeing and hearing several talks from Jason van Zyl et al about >> Maven3 >> and its greatness over Maven 2, I was wondering the following: >> >> a) is there a roadmap when Maven 3 is thought to be released ? (I know >> the >> "its done when its done", nevertheless, I was wondering if any roadmap >> exists). >> >> b) is there any releaseplans for Nexus / Hudson (plugin) / m2eclipse when >> Maven 3 comes out ? Meaning will these projects support Maven3 directly >> or >> will they be independently released from each other at any time ? >> >> c) Is it reasonable to start migrating now to Maven2 and with releasing >> Maven3 just drop that in and have little work to adjust the new version ? >> Or >> is it better to wait for Maven 3 and then do the migration step at that >> time >> ? >> >> The last question is crucial for us, as we have several hundreds of >> projects >> to cope with. >> >> I'm sorry if these questions are too naiv or something like that - its >> just >> important for "our" roadmap :-) >> >> Thanks for any help and input >> -- >> View this message in context: >> http://old.nabble.com/Migration-to-Maven--%21-tp28484923p28484923.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 >> >> > > -- View this message in context: http://old.nabble.com/Migration-to-Maven--%21-tp28484923p28485605.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
Migration to Maven ?!
Hello all, I need some helpful information and hope to find it here :-) In our company we consider to move from our current horrible build structure to Maven. With seeing and hearing several talks from Jason van Zyl et al about Maven3 and its greatness over Maven 2, I was wondering the following: a) is there a roadmap when Maven 3 is thought to be released ? (I know the "its done when its done", nevertheless, I was wondering if any roadmap exists). b) is there any releaseplans for Nexus / Hudson (plugin) / m2eclipse when Maven 3 comes out ? Meaning will these projects support Maven3 directly or will they be independently released from each other at any time ? c) Is it reasonable to start migrating now to Maven2 and with releasing Maven3 just drop that in and have little work to adjust the new version ? Or is it better to wait for Maven 3 and then do the migration step at that time ? The last question is crucial for us, as we have several hundreds of projects to cope with. I'm sorry if these questions are too naiv or something like that - its just important for "our" roadmap :-) Thanks for any help and input -- View this message in context: http://old.nabble.com/Migration-to-Maven--%21-tp28484923p28484923.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
