Re: How can I trigger a makefile through Maven? is there any plugin for this?
Hi! You might be interested in http://mojo.codehaus.org/exec-maven-plugin/ Or Google for 'maven exec plugin' and checkout the first hit. /Thomas On Wed, Apr 25, 2012 at 07:34, bettypop wrote: > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-can-I-trigger-a-makefile-through-Maven-is-there-any-plugin-for-this-tp5663921p5663921.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 > -- 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
How can I trigger a makefile through Maven? is there any plugin for this?
-- View this message in context: http://maven.40175.n5.nabble.com/How-can-I-trigger-a-makefile-through-Maven-is-there-any-plugin-for-this-tp5663921p5663921.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: Including Subprojects as jar files
This is more of a Hibernate problem than a Maven problem. We use Hibernate and Spring and in the configuration file that includes the HibernateSessionFactory, the reference to the hibernate configuration file is specified as "classpath:hibernate.cfg.xml" since the configuration file is in another project that is a dependency of the project doing the reference. I hope that this helps move your problem forward. The whole bean is: class="com.artifact_software.hibernate.session.alllazy.AllLazyFactoryBean" > classpath:hibernate.cfg.xml true true Ron On 24/04/2012 11:34 AM, nokha wrote: Hi, I'm facing a problem when including a subproject as a dependency in the POM of my project. Code is like the following: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";...> 4.0.0 com.test test1 1.0-SNAPSHOT war test1 http://maven.apache.org com.test test2 1.0-SNAPSHOT The problem is that test2 has hibernate mapping files, and currently when I start the application in dev mode they are not being loaded. Is there a trick for making project inclusion work? Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/Including-Subprojects-as-jar-files-tp5662412p5662412.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 -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven build failing
The maven-compiler-plugin version is wrong. maven-install-plugin:2.3.1 is ok maven-compiler-plugin:jar:3.0.4 is wrong should be 2.3.2 Check out http://maven.apache.org/plugins/index.html Ron On 24/04/2012 10:42 AM, Jeevan Reddy wrote: Hi, i am getting the following exception, while executing maven, [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] CustomerGrid [INFO] Commons [INFO] DTO [INFO] BaseGridPlug [INFO] JDBCGridPlug [INFO] WebServiceGridPlug [INFO] XMLGridPlug [INFO] OLAPGridPlug [INFO] SFDCGridPlug [INFO] GridData [INFO] GridServer [INFO] Lib [INFO] GridPlug [INFO] LaunchingScreen [INFO] ActionBridge [INFO] GridScan [INFO] GridMapApplet [INFO] GridControllerApplet [INFO] GridPortal [INFO] DunsServer [INFO] NetworkServer [INFO] JTest [INFO] CustomerGridEAR [INFO] [INFO] [INFO] Building CustomerGrid 5.0 [INFO] [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ CustomerGrid --- [INFO] Installing C:\dev\CG\com\nimaya\customergrid\pom.xml to C:\Users\jmankari\.m2\repository\com\nimaya\CustomerGrid\5.0\CustomerGrid-5.0.pom [INFO] [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ CustomerGrid --- Uploading: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/5.0/CustomerGrid-5.0.pom Uploaded: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/5.0/CustomerGrid-5.0.pom(16 KB at 537.6 KB/sec) Downloading: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/maven-metadata.xml Downloaded: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/maven-metadata.xml(298 B at 5.4 KB/sec) Uploading: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/maven-metadata.xml Uploaded: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/maven-metadata.xml(298 B at 18.2 KB/sec) [INFO] [INFO] [INFO] Building Commons 5.0 [INFO] [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.0.4 is missing, no dependency information available [INFO] [INFO] Reactor Summary: [INFO] [INFO] CustomerGrid .. SUCCESS [0.506s] [INFO] Commons ... FAILURE [0.025s] [INFO] DTO ... SKIPPED [INFO] BaseGridPlug .. SKIPPED [INFO] JDBCGridPlug .. SKIPPED [INFO] WebServiceGridPlug SKIPPED [INFO] XMLGridPlug ... SKIPPED [INFO] OLAPGridPlug .. SKIPPED [INFO] SFDCGridPlug .. SKIPPED [INFO] GridData .. SKIPPED [INFO] GridServer SKIPPED [INFO] Lib ... SKIPPED [INFO] GridPlug .. SKIPPED [INFO] LaunchingScreen ... SKIPPED [INFO] ActionBridge .. SKIPPED [INFO] GridScan .. SKIPPED [INFO] GridMapApplet . SKIPPED [INFO] GridControllerApplet .. SKIPPED [INFO] GridPortal SKIPPED [INFO] DunsServer SKIPPED [INFO] NetworkServer . SKIPPED [INFO] JTest . SKIPPED [INFO] CustomerGridEAR ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.863s [INFO] Finished at: Tue Apr 24 20:06:17 IST 2012 [INFO] Final Memory: 4M/15M [INFO] [ERROR] Plugin org.apache.maven.plugins:maven-compiler-plugin:3.0.4 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException C:\dev\CG\com\nimay
Including Subprojects as jar files
Hi, I'm facing a problem when including a subproject as a dependency in the POM of my project. Code is like the following: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";...> 4.0.0 com.test test1 1.0-SNAPSHOT war test1 http://maven.apache.org com.test test2 1.0-SNAPSHOT The problem is that test2 has hibernate mapping files, and currently when I start the application in dev mode they are not being loaded. Is there a trick for making project inclusion work? Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/Including-Subprojects-as-jar-files-tp5662412p5662412.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 build failing
Hi, i am getting the following exception, while executing maven, [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] CustomerGrid [INFO] Commons [INFO] DTO [INFO] BaseGridPlug [INFO] JDBCGridPlug [INFO] WebServiceGridPlug [INFO] XMLGridPlug [INFO] OLAPGridPlug [INFO] SFDCGridPlug [INFO] GridData [INFO] GridServer [INFO] Lib [INFO] GridPlug [INFO] LaunchingScreen [INFO] ActionBridge [INFO] GridScan [INFO] GridMapApplet [INFO] GridControllerApplet [INFO] GridPortal [INFO] DunsServer [INFO] NetworkServer [INFO] JTest [INFO] CustomerGridEAR [INFO] [INFO] [INFO] Building CustomerGrid 5.0 [INFO] [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ CustomerGrid --- [INFO] Installing C:\dev\CG\com\nimaya\customergrid\pom.xml to C:\Users\jmankari\.m2\repository\com\nimaya\CustomerGrid\5.0\CustomerGrid-5.0.pom [INFO] [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ CustomerGrid --- Uploading: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/5.0/CustomerGrid-5.0.pom Uploaded: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/5.0/CustomerGrid-5.0.pom(16 KB at 537.6 KB/sec) Downloading: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/maven-metadata.xml Downloaded: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/maven-metadata.xml(298 B at 5.4 KB/sec) Uploading: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/maven-metadata.xml Uploaded: file:///C:/dev/CG/com/nimaya/customergrid/ext/com/nimaya/CustomerGrid/maven-metadata.xml(298 B at 18.2 KB/sec) [INFO] [INFO] [INFO] Building Commons 5.0 [INFO] [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.0.4 is missing, no dependency information available [INFO] [INFO] Reactor Summary: [INFO] [INFO] CustomerGrid .. SUCCESS [0.506s] [INFO] Commons ... FAILURE [0.025s] [INFO] DTO ... SKIPPED [INFO] BaseGridPlug .. SKIPPED [INFO] JDBCGridPlug .. SKIPPED [INFO] WebServiceGridPlug SKIPPED [INFO] XMLGridPlug ... SKIPPED [INFO] OLAPGridPlug .. SKIPPED [INFO] SFDCGridPlug .. SKIPPED [INFO] GridData .. SKIPPED [INFO] GridServer SKIPPED [INFO] Lib ... SKIPPED [INFO] GridPlug .. SKIPPED [INFO] LaunchingScreen ... SKIPPED [INFO] ActionBridge .. SKIPPED [INFO] GridScan .. SKIPPED [INFO] GridMapApplet . SKIPPED [INFO] GridControllerApplet .. SKIPPED [INFO] GridPortal SKIPPED [INFO] DunsServer SKIPPED [INFO] NetworkServer . SKIPPED [INFO] JTest . SKIPPED [INFO] CustomerGridEAR ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.863s [INFO] Finished at: Tue Apr 24 20:06:17 IST 2012 [INFO] Final Memory: 4M/15M [INFO] [ERROR] Plugin org.apache.maven.plugins:maven-compiler-plugin:3.0.4 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException C:\dev\CG\com\nimaya\customergrid> what should i do? Regards, -Jeevan Reddy.
Re: How to replicate company internal repository?
> We use a internal Nexus repository. Now I want to set up an isolated test > environment. What's the best way to replicate the whole internal repository > into my Nexus? I read this as "...Nexus... Nexus... Nexus..." Why are you asking this here? Please use the Nexus Users list for such queries. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to replicate company internal repository?
On 24/04/2012 8:59 PM, hujirong wrote: Hi We use a internal Nexus repository. Now I want to set up an isolated test environment. What's the best way to replicate the whole internal repository into my Nexus? Why? What are you trying to do with a separate repo? Ron Thanks Jirong -- View this message in context: http://maven.40175.n5.nabble.com/How-to-replicate-company-internal-repository-tp5663623p5663623.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 -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to replicate company internal repository?
Hi We use a internal Nexus repository. Now I want to set up an isolated test environment. What's the best way to replicate the whole internal repository into my Nexus? Thanks Jirong -- View this message in context: http://maven.40175.n5.nabble.com/How-to-replicate-company-internal-repository-tp5663623p5663623.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: Parent POM entires and Effective POM
My only use for versions specified by property is where the suite of dependencies are all the same version. Properties is the only way right now to handle that. Pom v5 should have something better when we get to it shouldn't it, eh! On Tuesday, 24 April 2012, Wayne Fay wrote: > > way is a good idea. I have seen people refer to a mystical "depMgmt" > > element but see no mention of it in the Maven POM Reference. Anybody know > > the details? > > This is what you are looking for: > http://maven.apache.org/pom.html#Dependency_Management > > And more documentation in the Sonatype book: > > http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-project-dependencies.html > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
[ANN] Php Maven Plugin 2.0 released.
Hi, The "Maven for PHP" team proudly announces the release of Version 2.0.0 of the PHP Maven plugin set (depending on maven 3). Details about the release notes can be found in our google groups: https://groups.google.com/forum/?fromgroups#!topic/maven-for-php/Z9sZ4xoWUoQ The php plugins enables You to fully use maven lifecycle on php language projects. It uses PHPUnit for testing and PHPDoc (V1 and V2-alpha) for report/doc generation. For packaging it uses the phar archive format, introduced in PHP 5.2. We have imported many pear projects into our repository alongside with PHPUnit and PHPDoc support and more are following. Notice that this plugin is not part of the apache team or maven central. The php-maven repository setup can be found here: http://www.php-maven.org/prepare.html There is a m2e lifecycle binding too. Details on eclipse support can be found at the homepage: http://www.php-maven.org/tags/2.0.0/tut-usingeclipse.html Enjoy, The "Maven for PHP" team
Re: Parent POM entires and Effective POM
Wayne Fay wrote:
>> Specifying versions in module level POMs opens the door to a module
>> having the wrong version during the build which can show up as a method
>> not found if the module was built with a version later than the one
>> provided at runtime.
>
> I never said that I expect the module level POMs to have the version.
> They should inherit that from a (top) parent which should have the
> version in a dependentManagement section.
>
> I simply do not believe there is much to gain from having this in the
> parent (which is what he seems to be doing):
> 1.2.3
> ...${my.dep.version}
http://repo1.maven.org/maven2/com/thoughtworks/xstream/xstream-
parent/1.4.2/xstream-parent-1.4.2.pom
IMHO, it is much easier to get an overviewand it is a lot less error-prone
if some artifacts share the same version (e.g. ejb and ejb-client). And if I
look at our companies master POM with ~500 version entries ... ;-)
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Parent POM entires and Effective POM
> way is a good idea. I have seen people refer to a mystical "depMgmt" > element but see no mention of it in the Maven POM Reference. Anybody know > the details? This is what you are looking for: http://maven.apache.org/pom.html#Dependency_Management And more documentation in the Sonatype book: http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-project-dependencies.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to get an URL encoded version of a property?
Hello, say I want to reuse some POM or system property as parameter in another place in the POM but need it URL encoded. Does anyone know a Maven "magic" to achieve this? Programming a plugin to encode a given list of properties and provide them under a different name seems no biggy, but I would like to know if there are other, better or easier options :-D . Regards Mirko -- Sent from my phone http://illegalstateexception.blogspot.com http://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/
Re: How to add additional info to the MANIFEST.MF
Hi
You have not configured your project to be an EAR project.
You need to add the following line to your POM, otherwise
maven-ear-plugin is never run, as can be seen in the log you provided.
ear
On 2012-04-24 19:58, hujirong wrote:
> I tried, didn't work.
>
> Below is my POM and build output. There is no maven-ear-plugin definition in
> the parent POM.
>
>
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
>
>
> com.nbfg.max.maven
> max-wesb-pom
> 0.0.4-SNAPSHOT
>
>
> com.nbfg.max.wesb
> CDIPubSubMgmtMed
> 0.0.1-SNAPSHOT
> CDIPubSubMgmtMed Mediation
>
>
>
>
> maven-ear-plugin
>
>
>
>
> true
>
>
>
> ${maven.build.timestamp}
>
> NBFG
>
>
>
>
>
>
>
>
>
>
> com.ibm.ws.sca.sdoplugins
> sdo_api
> ${wid.version}
> system
>
> ${was.home}/feature_packs/sca/sdoplugins/sdo_api.jar
>
>
>
>
> com.nbfg.max.wesb
> ClientServicesBOLib
> 0.0.1-SNAPSHOT
>
>
> com.nbfg.max.wesb
> ClientInfoMgmtLib
> 0.0.1-SNAPSHOT
>
>
> com.nbfg.max.wesb
> CDIPubSubMgmtLib
> 0.0.1-SNAPSHOT
>
>
> com.nbfg.max.wesb
> CDIPubSubMgmtBOLib
> 0.0.1-SNAPSHOT
>
>
> com.nbfg.max.wesb
> CDIServiceMgmtLib
> 0.0.1-SNAPSHOT
>
>
> com.nbfg.max.wesb
> ClientInfoEventLib
> 0.0.1-SNAPSHOT
>
>
>
>
>
>
>
>
>
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building CDIPubSubMgmtMed Mediation 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ CDIPubSubMgmtMed
> ---
> [INFO] Deleting
> C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed
> [INFO]
> [INFO] --- build-helper-maven-plugin:1.7:regex-property (regex-property) @
> CDIPubSubMgmtMed ---
> [INFO] Setting property 'portable.artifact.path' to
> 'C:/Workspace/WID/CDIPubSubMgmtMed/../build/target/CDIPubSubMgmtMed/CDIPubSubMgmtMed-0.0.1-SNAPSHOT.ear'.
> [INFO]
> [INFO] --- build-helper-maven-plugin:1.7:add-source (add-source) @
> CDIPubSubMgmtMed ---
> [INFO] Source directory: C:\Workspace\WID\CDIPubSubMgmtMed\gen\src added.
> [INFO]
> [INFO] --- build-helper-maven-plugin:1.7:add-resource (add-resource) @
> CDIPubSubMgmtMed ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
> CDIPubSubMgmtMed ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory
> C:\Workspace\WID\CDIPubSubMgmtMed\src\main\resources
> [INFO] Copying 20 resources
> [INFO] Copying 1 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
> CDIPubSubMgmtMed ---
> [WARNING] File encoding has not been set, using platform encoding Cp1252,
> i.e. build is platform dependent!
> [INFO] Compiling 2 source files to
> C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed\classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:testResources
> (default-testResources) @ CDIPubSubMgmtMed ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory
> C:\Workspace\WID\CDIPubSubMgmtMed\src\test\resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testC
Re: Parent POM entires and Effective POM
> Specifying versions in module level POMs opens the door to a module
> having the wrong version during the build which can show up as a method
> not found if the module was built with a version later than the one
> provided at runtime.
I never said that I expect the module level POMs to have the version.
They should inherit that from a (top) parent which should have the
version in a dependentManagement section.
I simply do not believe there is much to gain from having this in the
parent (which is what he seems to be doing):
1.2.3
...${my.dep.version}
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Parent POM entires and Effective POM
Hi again, > I have seen people refer to a mystical "depMgmt" element but see no > mention of it in the Maven POM Reference. Heh, I should do my research properly. Looks like people are just abbreviating "dependencyManagement" which does exist in the POM reference: "dependencyManagement: is used by POMs to help manage dependency information across all of its children. If the my-parent project uses dependencyManagement to define a dependency on junit:junit:4.0, then POMs inheriting from this one can set their dependency giving the groupId=junit and artifactId=junit only, then Maven will fill in the version set by the parent." I'll have to give it a try! Sorry for the noise, Curtis On Tue, Apr 24, 2012 at 1:01 PM, Curtis Rueden wrote: > Hi everyone, > > > On Tue, Apr 24, 2012 at 12:51 PM, Ron Wheeler < > rwhee...@artifact-software.com> wrote: > >> If you have the same dependency in many modules and you want to ensure >> that all developers are using the same version >> > > This seems like an extremely common, if not ubiquitous, requirement to me. > > > >> Specifying versions in module level POMs opens the door to a module >> having the wrong version during the build which can show up as a method not >> found if the module was built with a version later than the one provided at >> runtime. >> > > I agree. This is the sort of thing the maven-enforcer-plugin is designed > to detect at build time, yes? > > http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html > > I haven't set it up yet for my team's projects, but am planning to do so > soon. At the moment we are using properties to define version numbers, > which is ugly and does not fully solve the problem anyway, since it does > enforce anyone to use those properties in their submodules. > > Alternately (or perhaps in addition), it is not clear to me whether it is > possible to specify dependency versions in a parent POM, which would be > automatically inherited by children, and if so, whether doing things this > way is a good idea. I have seen people refer to a mystical "depMgmt" > element but see no mention of it in the Maven POM Reference. Anybody know > the details? > > Regards, > Curtis > > > > On Tue, Apr 24, 2012 at 12:51 PM, Ron Wheeler < > rwhee...@artifact-software.com> wrote: > >> On 24/04/2012 1:24 PM, Wayne Fay wrote: >> >>> The parent has a 1.0 with no RELEASE OR SNAPSHOTs and the child poms do not specify the version explicitly. >>> Unless you are actively making a release, your version should almost >>> always have the -SNAPSHOT qualifier appended to it. So if you are >>> working on version 1.0, then your pom should show version 1.0-SNAPSHOT >>> until the brief moment in time when you perform the release -- then it >>> will be 1.0 -- and then immediately after it should bump to version >>> 1.1-SNAPSHOT. >>> >>> 1.2.1.**RELEASE 1.1.0.**BUILD-SNAPSHOT >>> I can't speak for everyone, but I am definitely not a fan of declaring >>> dependency versions in a tag like this. It just makes things more >>> complicated. When I open a pom, I want to find the version right there >>> along with the GroupId and ArtifactId in or >>> . Managing versions with properties is not a >>> best practice IMO. >>> >> If you have the same dependency in many modules and you want to ensure >> that all developers are using the same version since you likely want it as >> "provided", you will have a lot of maintenance to do. >> >> My "management principle" is that version selection is a project >> management/team function and the developers of individual modules should >> not be concerned about the versions of shared dependencies. If they find a >> problem with the version selected by the team, then this should be raised >> to the team level. >> >> Specifying versions in module level POMs opens the door to a module >> having the wrong version during the build which can show up as a method not >> found if the module was built with a version later than the one provided at >> runtime. >> >> Ron >> >> >> Wayne >>> >>> --**--** >>> - >>> To unsubscribe, e-mail: >>> users-unsubscribe@maven.**apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >>> >> >> -- >> Ron Wheeler >> President >> Artifact Software Inc >> email: rwhee...@artifact-software.com >> skype: ronaldmwheeler >> phone: 866-970-2435, ext 102 >> >> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > >
Re: Parent POM entires and Effective POM
Hi everyone, On Tue, Apr 24, 2012 at 12:51 PM, Ron Wheeler < rwhee...@artifact-software.com> wrote: > If you have the same dependency in many modules and you want to ensure > that all developers are using the same version > This seems like an extremely common, if not ubiquitous, requirement to me. > Specifying versions in module level POMs opens the door to a module > having the wrong version during the build which can show up as a method not > found if the module was built with a version later than the one provided at > runtime. > I agree. This is the sort of thing the maven-enforcer-plugin is designed to detect at build time, yes? http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html I haven't set it up yet for my team's projects, but am planning to do so soon. At the moment we are using properties to define version numbers, which is ugly and does not fully solve the problem anyway, since it does enforce anyone to use those properties in their submodules. Alternately (or perhaps in addition), it is not clear to me whether it is possible to specify dependency versions in a parent POM, which would be automatically inherited by children, and if so, whether doing things this way is a good idea. I have seen people refer to a mystical "depMgmt" element but see no mention of it in the Maven POM Reference. Anybody know the details? Regards, Curtis On Tue, Apr 24, 2012 at 12:51 PM, Ron Wheeler < rwhee...@artifact-software.com> wrote: > On 24/04/2012 1:24 PM, Wayne Fay wrote: > >> The parent has a 1.0 with no RELEASE OR SNAPSHOTs and the >>> child poms do not specify the version explicitly. >>> >> Unless you are actively making a release, your version should almost >> always have the -SNAPSHOT qualifier appended to it. So if you are >> working on version 1.0, then your pom should show version 1.0-SNAPSHOT >> until the brief moment in time when you perform the release -- then it >> will be 1.0 -- and then immediately after it should bump to version >> 1.1-SNAPSHOT. >> >> 1.2.1.**RELEASE >>> 1.1.0.**BUILD-SNAPSHOT >>> >> I can't speak for everyone, but I am definitely not a fan of declaring >> dependency versions in a tag like this. It just makes things more >> complicated. When I open a pom, I want to find the version right there >> along with the GroupId and ArtifactId in or >> . Managing versions with properties is not a >> best practice IMO. >> > If you have the same dependency in many modules and you want to ensure > that all developers are using the same version since you likely want it as > "provided", you will have a lot of maintenance to do. > > My "management principle" is that version selection is a project > management/team function and the developers of individual modules should > not be concerned about the versions of shared dependencies. If they find a > problem with the version selected by the team, then this should be raised > to the team level. > > Specifying versions in module level POMs opens the door to a module having > the wrong version during the build which can show up as a method not found > if the module was built with a version later than the one provided at > runtime. > > Ron > > > Wayne >> >> --**--**- >> To unsubscribe, e-mail: >> users-unsubscribe@maven.**apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >> > > -- > Ron Wheeler > President > Artifact Software Inc > email: rwhee...@artifact-software.com > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
Re: How to add additional info to the MANIFEST.MF
I tried, didn't work.
Below is my POM and build output. There is no maven-ear-plugin definition in
the parent POM.
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.nbfg.max.maven
max-wesb-pom
0.0.4-SNAPSHOT
com.nbfg.max.wesb
CDIPubSubMgmtMed
0.0.1-SNAPSHOT
CDIPubSubMgmtMed Mediation
maven-ear-plugin
true
${maven.build.timestamp}
NBFG
com.ibm.ws.sca.sdoplugins
sdo_api
${wid.version}
system
${was.home}/feature_packs/sca/sdoplugins/sdo_api.jar
com.nbfg.max.wesb
ClientServicesBOLib
0.0.1-SNAPSHOT
com.nbfg.max.wesb
ClientInfoMgmtLib
0.0.1-SNAPSHOT
com.nbfg.max.wesb
CDIPubSubMgmtLib
0.0.1-SNAPSHOT
com.nbfg.max.wesb
CDIPubSubMgmtBOLib
0.0.1-SNAPSHOT
com.nbfg.max.wesb
CDIServiceMgmtLib
0.0.1-SNAPSHOT
com.nbfg.max.wesb
ClientInfoEventLib
0.0.1-SNAPSHOT
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building CDIPubSubMgmtMed Mediation 0.0.1-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ CDIPubSubMgmtMed
---
[INFO] Deleting
C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed
[INFO]
[INFO] --- build-helper-maven-plugin:1.7:regex-property (regex-property) @
CDIPubSubMgmtMed ---
[INFO] Setting property 'portable.artifact.path' to
'C:/Workspace/WID/CDIPubSubMgmtMed/../build/target/CDIPubSubMgmtMed/CDIPubSubMgmtMed-0.0.1-SNAPSHOT.ear'.
[INFO]
[INFO] --- build-helper-maven-plugin:1.7:add-source (add-source) @
CDIPubSubMgmtMed ---
[INFO] Source directory: C:\Workspace\WID\CDIPubSubMgmtMed\gen\src added.
[INFO]
[INFO] --- build-helper-maven-plugin:1.7:add-resource (add-resource) @
CDIPubSubMgmtMed ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
CDIPubSubMgmtMed ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
C:\Workspace\WID\CDIPubSubMgmtMed\src\main\resources
[INFO] Copying 20 resources
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
CDIPubSubMgmtMed ---
[WARNING] File encoding has not been set, using platform encoding Cp1252,
i.e. build is platform dependent!
[INFO] Compiling 2 source files to
C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed\classes
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources
(default-testResources) @ CDIPubSubMgmtMed ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
C:\Workspace\WID\CDIPubSubMgmtMed\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @
CDIPubSubMgmtMed ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.7.2:test (default-test) @
CDIPubSubMgmtMed ---
[INFO] No tests to run.
[INFO] Surefire report directory:
C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed\surefire-reports
---
T E S T S
Re: Parent POM entires and Effective POM
On 24/04/2012 1:24 PM, Wayne Fay wrote: The parent has a 1.0 with no RELEASE OR SNAPSHOTs and the child poms do not specify the version explicitly. Unless you are actively making a release, your version should almost always have the -SNAPSHOT qualifier appended to it. So if you are working on version 1.0, then your pom should show version 1.0-SNAPSHOT until the brief moment in time when you perform the release -- then it will be 1.0 -- and then immediately after it should bump to version 1.1-SNAPSHOT. 1.2.1.RELEASE 1.1.0.BUILD-SNAPSHOT I can't speak for everyone, but I am definitely not a fan of declaring dependency versions in a tag like this. It just makes things more complicated. When I open a pom, I want to find the version right there along with the GroupId and ArtifactId in or . Managing versions with properties is not a best practice IMO. If you have the same dependency in many modules and you want to ensure that all developers are using the same version since you likely want it as "provided", you will have a lot of maintenance to do. My "management principle" is that version selection is a project management/team function and the developers of individual modules should not be concerned about the versions of shared dependencies. If they find a problem with the version selected by the team, then this should be raised to the team level. Specifying versions in module level POMs opens the door to a module having the wrong version during the build which can show up as a method not found if the module was built with a version later than the one provided at runtime. Ron Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Parent POM entires and Effective POM
> The parent has a 1.0 with no RELEASE OR SNAPSHOTs and the > child poms do not specify the version explicitly. Unless you are actively making a release, your version should almost always have the -SNAPSHOT qualifier appended to it. So if you are working on version 1.0, then your pom should show version 1.0-SNAPSHOT until the brief moment in time when you perform the release -- then it will be 1.0 -- and then immediately after it should bump to version 1.1-SNAPSHOT. > 1.2.1.RELEASE > 1.1.0.BUILD-SNAPSHOT I can't speak for everyone, but I am definitely not a fan of declaring dependency versions in a tag like this. It just makes things more complicated. When I open a pom, I want to find the version right there along with the GroupId and ArtifactId in or . Managing versions with properties is not a best practice IMO. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Parent POM entires and Effective POM
Yes. I just saw this note under 'Best Practices' "Maven uses the depth of a dependency in the tree when resolving conflicts using a nearest-wins approach. Using the dependency *grouping technique above pushes those dependencies one level down in the tree*. Keep this in mind when choosing between grouping in a pom or using dependencyManagement in a parent POM". I was grouping the dependencies in the parent. Thanks for the information. -- View this message in context: http://maven.40175.n5.nabble.com/Parent-POM-entires-and-Effective-POM-tp5662422p5662621.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: Parent POM entires and Effective POM
Could it perhaps be caused by putting the dependency in the parent as a dependency rather than a version in the dependency management section? You might want to reread the Maven documentation or one of the books about using a parent POM to manage versions. It works fine if you do it right. Ron On 24/04/2012 12:10 PM, Wayne Fay wrote: In the Web Module (that inherits from the parent POM), the effective POM shows a different older version. I thought this could be because of Spring Projects and their dependency. Later, when I copied the POM entries from Parent and pasted in the Web Module's POM, I got the right versions. I am using Spring STS with Maven 3.0.3. What is the version number of the parent and child from their pom.xml files? If the versions are not snapshots, then Maven is most likely doing things properly and you do not recognize some important aspects of releases vs snapshots. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Parent POM entires and Effective POM
The parent has a 1.0 with no RELEASE OR SNAPSHOTs and the child poms do not specify the version explicitly. These are the projects that I am not getting correctly. 1.2.1.RELEASE 1.1.0.BUILD-SNAPSHOT 2.1.0.RELEASE 3.1.0.RELEASE 2.2.0.BUILD-SNAPSHOT when I specify these properties in the web module's POM, the effective POM reflects the same. I would read further on the topic outlined by you. -- View this message in context: http://maven.40175.n5.nabble.com/Parent-POM-entires-and-Effective-POM-tp5662422p5662592.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 3.0 and EJB 2.0 or 1.0
> The current ejb plugin can only compile EJB project into a normal JAR but it > is not some thing that can be deployed on WAS 7.0 as an EJB JAR. it does not > generates stubs and skeletons. You probably just need to write all that code (and the configuration etc) yourself and then just use the jar plugin. It is also possible that there is another plugin somewhere on the Internet which would be helpful, but you'd need to check Google. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Parent POM entires and Effective POM
> In the Web Module (that inherits from the parent POM), the effective POM > shows a different older version. I thought this could be because of Spring > Projects and their dependency. Later, when I copied the POM entries from > Parent and pasted in the Web Module's POM, I got the right versions. I am > using Spring STS with Maven 3.0.3. What is the version number of the parent and child from their pom.xml files? If the versions are not snapshots, then Maven is most likely doing things properly and you do not recognize some important aspects of releases vs snapshots. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Parent POM entires and Effective POM
Hi, I have defined a Parent POM to use the latest versions of Spring Integration and Spring Data projects In the Web Module (that inherits from the parent POM), the effective POM shows a different older version. I thought this could be because of Spring Projects and their dependency. Later, when I copied the POM entries from Parent and pasted in the Web Module's POM, I got the right versions. I am using Spring STS with Maven 3.0.3. I am relatively new to Maven and am not sure whether I am not following any standards. Would share the POM entries, if required. Thanks -- View this message in context: http://maven.40175.n5.nabble.com/Parent-POM-entires-and-Effective-POM-tp5662422p5662422.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: How to add additional info to the MANIFEST.MF
> The current EAR file only has the first three lines info. How can I add the > next four lines in BOLD? I am using a parent POM which is not created by me. Google for "maven manifest.mf" leads me to: http://maven.apache.org/guides/mini/guide-manifest.html With a link to: http://maven.apache.org/shared/maven-archiver/index.html Which tells the user how to add such data via . Since this is an ear, you will add configuration to the maven-ear-plugin entry in your pom. Here is an example if your project was a jar -- just adapt it slightly: http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html Google knows about all of this. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to add additional info to the MANIFEST.MF
Hi The current EAR file only has the first three lines info. How can I add the next four lines in BOLD? I am using a parent POM which is not created by me. Thanks Jirong Manifest-Version: 1.0 DeployVersion: 7.0.0.0 Created-By: 1.5.0 (IBM Corporation) *Implementation-Vendor: NBFG Built-By: NBFG Implementation-Version: 20120404_1130 Implementation-Title: CDIPubSubMgmtMed* -- View this message in context: http://maven.40175.n5.nabble.com/How-to-add-additional-info-to-the-MANIFEST-MF-tp5662221p5662221.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: Profile activation for mac and linux
I know this is an old thread, but for the lurkers of the internets, I might post a possible answer. In stead of using "family" as the identifier, one could use "name" - either in stead of or in addition to "family". The following should thus be an unambigious activation unix Linux You can get the os name by running "mvn help:system |grep os.name" -- View this message in context: http://maven.40175.n5.nabble.com/Profile-activation-for-mac-and-linux-tp3263043p5661715.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] Re: Mirroring repo1.maven.apache.org
And in the interests of keeping ASF vendor neutral, There are at leaste three repository managers equally capable of providing 95% of what people need (they disagree on the remaining 5% either being needed or how to solve) In alphabetical order, so as not to imply any preference: Archivia by Apache Artifactory by JFrog Nexus by Sonatype I have used all three in different situations, and it's swings and roundabouts for the advanced features. I would not reject any of them out of hand based on my experience with them. On 24 April 2012 02:23, Andrew Hughes wrote: > You asked... > > I agree that the Nexus pull only when needed is nice. But there are other > concerns too. The real question is there a strong reason for not using > rsync > other than use Nexus. > > > Yes. > > 1. I use nexus so that I limit the bandwidth I share with YOU (from > hosted repositories). No one likes a 'road hog' :) > 2. Nexus will allow you to proxy/mirror a lot more than one repository, > it will also allow you to place rules on repositories and additional > configuration. > 3. Nexus will be useful as it provides you with your own maven > repository to deploy/release your own artifacts/projects too. > 4. Nexus can aggregate a bunch of repositories into "one" virtual > repository, this will make life easier for your developers as they only > ever need 1 repository. > 5. Nexus can provide you with a place to "upload"/"deploy" artifacts > that are not in a public repository so that they can be shared with your > team members. > 6. Because its "the standard", if you want to re-invent the wheel that's > cool, it'll do very much the same job. Alternatively there is a bunch of > documentation out there about nexus and its application, setup, usage, > settings.xml e.t.c Just in case you get hit by a bus or win the > lottery > next week you'll be a lot less vulnerable. > > > Hope that helps :) > > > > On Mon, Apr 23, 2012 at 1:26 AM, Jason Pyeron wrote: > > > > -Original Message- > > > From: Brian Topping > > > Sent: Sunday, April 22, 2012 11:32 > > > > > > On Apr 22, 2012, at 10:26 AM, Jason Pyeron wrote: > > > > > > > 1. Is mirrors.ibiblio.org a good source for mirroring > > > repo1.maven.apache.org? > > > > 2. is there a strong reason not use rsync? > > > > > > Mirroring a repository like that is considered very bad form > > > and will probably get your servers blacklisted. > > > > This caught me off guard. Is that not the point of ibiblio.orgsupporting > > rsync? > > We have a daily rsync set up with them for other projects. > > > > > > > > I don't have the benefit of other posts you may have made on > > > this subject, > > > > No other posts on this topic. > > > > > but unless you are hosting half the known world > > > of developers, why wouldn't you just use a repository? > > > > The mirror team has bandwith management infrastructure inplace. They did > > not > > want to modify their system to support Nexus for Nexus sake. We have a > > nexus > > server on our dev lan already. Our dev lan does not have direct access to > > the > > internet. > > > > > It > > > makes things so much simpler with your builds since real > > > world projects generally do not pull from just central. > > > > It was listed on the bandwidth report. > > > > > Having a half-dozen repositories in your build is a great way > > > to have it constantly slow (and even slower at times when any > > > one of those repositories is offline). Caching those > > > repositories through Nexus insulates you from their downtime, > > > without having to soak their bandwidth for files you will never use. > > > > I agree that the Nexus pull only when needed is nice. But there are other > > concerns too. The real question is there a strong reason for not using > > rsync > > other than use Nexus. > > > > > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > - - > > - Jason Pyeron PD Inc. http://www.pdinc.us - > > - Principal Consultant 10 West 24th Street #100- > > - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - > > - - > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > This message is copyright PD Inc, subject to license 20080407P00. > > > > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
Re: Maven 3.0 and EJB 2.0 or 1.0
Are you seriously still using EJB-1.0? The crap which instantly caused lots of people puking back in 1999? I'm aware that a few poor developers still need to clean up the mess in old projects, but is there even a supported container for those things? I think EJB-3.0 got introduced in early 2006 - and that's already quite some time ago. Which target container are you using? It might be much easier to just update to at least EJB-3.0. I doubt there is any _maintained_ container available who has only EJB-1.x support... LieGrue, strub - Original Message - > From: sarmahdi > To: users@maven.apache.org > Cc: > Sent: Tuesday, April 24, 2012 10:49 AM > Subject: Maven 3.0 and EJB 2.0 or 1.0 > > Hello guys, > > How can I mavenize a project that uses older versions of EJB like 1.0 or > 2.0. I know the plugin does support EJB 2.0+ but it has limited > capabilities. How did people work around this issue. I am sure there must be > a lot of projects that used EJB 2.0 at least if not 1.0 as Maven has been > around for 10 years almost now. > > The current ejb plugin can only compile EJB project into a normal JAR but it > is not some thing that can be deployed on WAS 7.0 as an EJB JAR. it does not > generates stubs and skeletons. > > I would really like to know, What did maven users do for their EJB 1.0 > projects? > > Thanks for any replies. > > Syed Mahdi. > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Maven-3-0-and-EJB-2-0-or-1-0-tp5661362p5661362.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
Re: Are, ALWAYS active? (interval:5 not working)
On 24 April 2012 03:02, Andrew Hughes wrote: > OK, I found a way to confirm... > > are always active Exactly what I wanted as documented > :) > > However, the problem persisted... until... > > I noticed that builds on the command line worked fine, as did 'install' > e.t.c from within eclipse. However, the m2eclipse dependencies refused to > update. Is it possible that the eclipse plugin has some internal cache that > holds into dependencies and overrides those from maven? I also tried maven > -> update dependencies, fail, I also did maven -> update project > configuration, fail then I did maven -> update project configuration + > force update of Snapshot / Releases. SUCCESS. > > Why would m2e have a difference update/cache policy on dependencies to that > of maven? > I would suspect because the session never ends, and there is checking once per session only if the update policy demands it You can get the very same behaviour from a very very long running Maven build, where the snapshot is resolved once during the build only, even if plugins further in the build do explicit resolves. > > Cheers. > > > > On Tue, Apr 24, 2012 at 11:06 AM, Richard W. Eggert II < > richard.egg...@gmail.com> wrote: > > > On 4/23/2012 9:15 PM, Benson Margulies wrote: > > > >> On Mon, Apr 23, 2012 at 9:00 PM, Andrew Hughes > >> wrote: > >> > >>> Hi All, > >>> > >>> I have configured the following to perform (local) snapshot updates > every > >>> 5mins... unfortunately the dependencies DO NOT update at the prescribed > >>> 5min interval. Could it be that the do not ALWAYS > >>> activate? I do have a specific -P dev (project defined) profile enabled > >>> while building, will this deactivate the settings.xml? > Or > >>> any other circumstances for that matter? > >>> > >>> If anyone has a better way of doing this or if there is a problem with > my > >>> settings below, I'm all ear's :) > >>> > >> Or wars? > >> > >> activeProfiles are only active until some explicit profile is > >> activated from the command line, I believe. You need to make your > >> profile use an activation that will always be satisfied instead. > >> > >> > >> > > If I recall correctly, you can disable an active profile by explicitly > > disabling it by prefixing the name with '!'. For example, if your active > > profile is named "foo", you could run the "package" goal with the profile > > disabled like so: > > mvn package -P !foo > > > > Rich Eggert > > > > > > --**--**- > > To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org< > users-unsubscr...@maven.apache.org> > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
Re: Incorrectly generated URLs in pom's using maven release plugin
Hi Dennis, On Mon, Apr 23, 2012 at 9:54 PM, Dennis Lundberg wrote: > > > > There are some wrong urls in the pom.xml files, namely in the scm > section. > > (I am not sure what impact of this is). It is about: > > -the pom.xml in the project root --> seems incorrect. > > > Not sure what happened to this one... > Do you envisage that this will pose any problems further down the line, other than something which could be considered simply as a typo of sorts? I am speaking from RM perspective and whether this justifies rolling another RC. What do you think? > > > -the sources-dist/pom.xml --> like above, plus: url, connection and > > developerConnection have 'trunk' postfixed. > > -the subprojects (store implementations) pom.xml --> like above. > > This is because the SCM URLs that you have in your subprojects in trunk > are wrong. They are currently pointing to > http://svn.apache.org/viewvc/gora/trunk/ > when they should be pointing to > http://svn.apache.org/viewvc/gora/trunk// > > OK I will update this in the project trunk, I suppose the same stands for this as does for the above! Again, thanks in advance for your input. Best Lewis
Maven 3.0 and EJB 2.0 or 1.0
Hello guys, How can I mavenize a project that uses older versions of EJB like 1.0 or 2.0. I know the plugin does support EJB 2.0+ but it has limited capabilities. How did people work around this issue. I am sure there must be a lot of projects that used EJB 2.0 at least if not 1.0 as Maven has been around for 10 years almost now. The current ejb plugin can only compile EJB project into a normal JAR but it is not some thing that can be deployed on WAS 7.0 as an EJB JAR. it does not generates stubs and skeletons. I would really like to know, What did maven users do for their EJB 1.0 projects? Thanks for any replies. Syed Mahdi. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-3-0-and-EJB-2-0-or-1-0-tp5661362p5661362.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
[ANN] chronos-jmeter-maven-plugin 1.0 and chronos-report-maven-plugin 1.0 released
Hi, The Mojo team is pleased to announce the release of the chronos-jmeter-maven-plugin and chronos-report-maven-plugin version 1.0. Chronos enables You to test performance via JMeter, validate that relevant performance goals have been met, and create nice visualizations of the latest and historical testruns. The tests are being run as part of a Maven build, either continuously or ad hoc. This will allow a developer to integrate performancetesting into an existing project and performancetest continuously, typically as part of a nightly build. This will help to pinpoint performance problems: If You know when a performance problem was introduced, it is easier to find out which change in the codebase caused the performance degradation. Project site: http://mojo.codehaus.org/chronos To get this update, simply specify the version in your project's plugin configuration: build section: org.codehaus.mojo chronos-jmeter-maven-plugin 1.0 reporting section: org.codehaus.mojo chronos-jmeter-maven-plugin 1.0 See the documentation at http://mojo.codehaus.org/chronos for further details and configuration parameters. Release Notes See http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12536&version=18439 Enjoy, The Mojo team. Kent Solvsten
