Re: maven-assembly-plugin / Maven default folder layout
I would call it advancing insight. I can't think of an assembly which is only for unittesting (due to the src/test folder) and won't be attached the the MavenProject for deployment. For users it would make it clear: everything under /src/main are files required during compile time everything under /src/test are files required during test time everything under /src/it are files required during integration tests assembly descriptors doesn't cover one of these, so it should have its own folder. While Maven-core uses src/main/assembly for years doesn't mean that we could adjust our advice. Robert Op Sat, 08 Mar 2014 23:57:06 +0100 schreef Dennis Lundberg denn...@apache.org: Hi Robert, I was not thinking about scope here, just the directory structure of the project. We've used src/main/assembly for years now. Maven-core has its assembly descriptors in src/main/assembly. It seems strange to suddenly change it. In what way would our users benefit from this change? On Sat, Mar 8, 2014 at 10:41 PM, Robert Scholte rfscho...@apache.org wrote: Hi Dennis, an assembly will always result in an attachment, but there's no such thing as attaching with a scope. For that reason I wouldn't separate the assembly descriptors, it might cause invalid assumptions. Robert Op Sat, 08 Mar 2014 22:24:10 +0100 schreef Dennis Lundberg denn...@apache.org: Hi I agree with Karl Heinz that the Assembly Plugin should support the documented default directory. It seems that we disagree about what the preferred directory should be. I think it should be src/main/assembly/ because almost all assemblies I have ever seen are for the main part of a project. If someone wanted to create an assembly for the test part of a project I would recommend to place the assembly descriptor in src/test/assembly. On Fri, Mar 7, 2014 at 8:25 PM, Robert Scholte rfscho...@apache.org wrote: Hi, This is the standard (preferred) directory layout, so it doesn't have to be the default. I actually think that src/main/assembly/ should be src/assembly/, otherwise it would imply that there can also be a src/test/assembly/. I wouldn't separate the descriptors into different folders. Robert Op Fri, 07 Mar 2014 20:14:48 +0100 schreef Karl Heinz Marbaise khmarba...@gmx.de: Hi, I stumbled over a small thing. The page about the default folder layout https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html mentioned a location for the maven-assembly-plugin descriptors: src/main/assembly/ So the location is a suggestion to locate assembly descriptors but the maven-assembly-plugin itself does not have such a default value for that ? In my opinion the maven-assembly-plugin should have a default location as mentioned above (descriptors default value to search for src/main/assembly/ descriptors) or we should change the above description.. What do you thing ? Ideas ? Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin / Maven default folder layout
Am 2014-03-08 22:24, schrieb Dennis Lundberg: Hi I agree with Karl Heinz that the Assembly Plugin should support the documented default directory. It seems that we disagree about what the preferred directory should be. I think it should be src/main/assembly/ because almost all assemblies I have ever seen are for the main part of a project. If someone wanted to create an assembly for the test part of a project I would recommend to place the assembly descriptor in src/test/assembly. Dennis, neither do you have src/main/site and other resembling structures. There is no way to enforce that this assembly is part of a test cycle, moreover such a notion does not exist for assemblies. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
+1 and thanks for pushing this, Dennis! LieGrue, strub On Saturday, 8 March 2014, 23:50, Dennis Lundberg denn...@apache.org wrote: Hi, We solved 15 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=Htmlversion=19723 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1010/ https://repository.apache.org/content/repositories/maven-1010/org/apache/maven/plugins/maven-checkstyle-plugin/2.12/maven-checkstyle-plugin-2.12-source-release.zip Source release checksum(s): maven-checkstyle-plugin-2.12-source-release.zip sha1: 1d2c6435e214daa9bedce6d32871a8b7ac3f Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote is open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
+1 Regards, Hervé Le samedi 8 mars 2014 23:49:54 Dennis Lundberg a écrit : Hi, We solved 15 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=H tmlversion=19723 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127sta tus=1 Staging repo: https://repository.apache.org/content/repositories/maven-1010/ https://repository.apache.org/content/repositories/maven-1010/org/apache/mav en/plugins/maven-checkstyle-plugin/2.12/maven-checkstyle-plugin-2.12-source- release.zip Source release checksum(s): maven-checkstyle-plugin-2.12-source-release.zip sha1: 1d2c6435e214daa9bedce6d32871a8b7ac3f Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote is open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release ASF Parent POM version 14
+1 Op Thu, 06 Mar 2014 22:18:56 +0100 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Changes since the last release: http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEADr2=1434717diff_format=h Staging repo: https://repository.apache.org/content/repositories/orgapacheapache-1000/ https://repository.apache.org/content/repositories/orgapacheapache-1000/org/apache/apache/14/apache-14-source-release.zip Source release checksum: apache-14-source-release.zip sha1: 6bed0856a4cc8d9ee5f4481b8a1e0a4460076073 Staging site: http://maven.apache.org/pom-archives/asf-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release ASF Parent POM version 14
+1 LieGrue, strub On Thursday, 6 March 2014, 22:19, Hervé BOUTEMY herve.bout...@free.fr wrote: Hi, Changes since the last release: http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEADr2=1434717diff_format=h Staging repo: https://repository.apache.org/content/repositories/orgapacheapache-1000/ https://repository.apache.org/content/repositories/orgapacheapache-1000/org/apache/apache/14/apache-14-source-release.zip Source release checksum: apache-14-source-release.zip sha1: 6bed0856a4cc8d9ee5f4481b8a1e0a4460076073 Staging site: http://maven.apache.org/pom-archives/asf-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Filtering version 1.2
+1 LieGrue, strub On Saturday, 8 March 2014, 17:13, Hervé BOUTEMY herve.bout...@free.fr wrote: +1 Regards, Hervé Le jeudi 6 mars 2014 22:08:10 Robert Scholte a écrit : Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=187 29styleName=Html There is still 1 issue left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11761sta tus=1component=13380 Staging repo: https://repository.apache.org/content/repositories/maven-1009/ https://repository.apache.org/content/repositories/maven-1009/org/apache/mav en/shared/maven-filtering/1.2/maven-filtering-1.2-source-release.zip Source release checksum(s): maven-filtering-1.2-source-release.zip sha1: 50185091c5be24ee3a01296224d9d4eee77852c9 Staging site: http://maven.apache.org/shared-archives/maven-filtering-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 thanks, Robert - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
Hi, +1 from me Checked the sha1 of the downloaded artifact from staging repository. Checked a project which had an NPE with 2.11 version now the NPE is fixed (MCHECKSTYLE-205). Kind regards Karl-Heinz Marbaise Hi, We solved 15 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=Htmlversion=19723 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1010/ https://repository.apache.org/content/repositories/maven-1010/org/apache/maven/plugins/maven-checkstyle-plugin/2.12/maven-checkstyle-plugin-2.12-source-release.zip Source release checksum(s): maven-checkstyle-plugin-2.12-source-release.zip sha1: 1d2c6435e214daa9bedce6d32871a8b7ac3f Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote is open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
Hi, unfortunately i have to retire my +1 cause i found an issue in the integration tests (i was to fast with the send button sorry). Tested with Maven 3.0.5 and a clean local repository and got the following: [INFO] --- maven-invoker-plugin:1.8:integration-test (integration-test) @ maven-checkstyle-plugin --- [INFO] Building: check-fail/pom.xml [INFO] ..SUCCESS (8.2 s) [INFO] Building: check-pass/pom.xml [INFO] ..SUCCESS (4.1 s) [INFO] Building: check-tests-only/pom.xml [INFO] ..SUCCESS (2.8 s) [INFO] Building: checkstyle-goal/pom.xml [INFO] run script verify.groovy [INFO] ..SUCCESS (4.3 s) [INFO] Building: checkstyle-report/pom.xml [INFO] run script verify.groovy [INFO] ..SUCCESS (11.5 s) [INFO] Building: inlinerules/pom.xml [INFO] run script verify.groovy [INFO] ..FAILED (3.5 s) [INFO] The post-build script did not succeed. assert new File(basedir, 'target/checkstyle-checker.xml').exists() || | || false | /Users/kama/Downloads/maven-checkstyle-plugin-2.12/target/it/inlinerules /Users/kama/Downloads/maven-checkstyle-plugin-2.12/target/it/inlinerules/target/checkstyle-checker.xml Attached the full log file output Tested the same thing with Maven 3.1.1, Maven 3.2.1 and Maven 2.2.1 and got the same result. Sorry... Kind regards Karl-Heinz Marbaise + Error stacktraces are turned on. Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.7.0_21 Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: mac os x version: 10.8.5 arch: x86_64 Family: mac [DEBUG] Building Maven user-level plugin registry from: '/Users/kama/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/usr/share/java/apache-maven-2.2.1/conf/plugin-registry.xml' [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Example [INFO] Example Module [INFO] snapshot org.apache.maven.plugins:maven-checkstyle-plugin:2.12-SNAPSHOT: checking for updates from local.central [DEBUG] Connecting to repository: 'local.central' with url: 'file:///Users/kama/.m2/repository'. [DEBUG] repository metadata for: 'snapshot org.apache.maven.plugins:maven-checkstyle-plugin:2.12-SNAPSHOT' could not be found on repository: local.central [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] maven-checkstyle-plugin: using locally installed snapshot [DEBUG] Trying repository local.central [DEBUG] Connecting to repository: 'local.central' with url: 'file:///Users/kama/.m2/repository'. Downloading: file:///Users/kama/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.12-SNAPSHOT/maven-checkstyle-plugin-2.12-SNAPSHOT.pom [DEBUG] File: /Users/kama/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.12-SNAPSHOT/maven-checkstyle-plugin-2.12-SNAPSHOT.pom does not exist org.apache.maven.wagon.ResourceDoesNotExistException: File: /Users/kama/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.12-SNAPSHOT/maven-checkstyle-plugin-2.12-SNAPSHOT.pom does not exist at org.apache.maven.wagon.providers.file.FileWagon.fillInputData(FileWagon.java:70) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:546) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:427) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:382) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:216) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251) at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:277) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:205) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184) at org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1787) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:462) at
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
That's strange. I specificly ran the its before the release (using 3.0.5). Which OS are you running on? -- Dennis Lundberg Den 9 mar 2014 14:43 skrev Karl Heinz Marbaise khmarba...@gmx.de: Hi, unfortunately i have to retire my +1 cause i found an issue in the integration tests (i was to fast with the send button sorry). Tested with Maven 3.0.5 and a clean local repository and got the following: [INFO] --- maven-invoker-plugin:1.8:integration-test (integration-test) @ maven-checkstyle-plugin --- [INFO] Building: check-fail/pom.xml [INFO] ..SUCCESS (8.2 s) [INFO] Building: check-pass/pom.xml [INFO] ..SUCCESS (4.1 s) [INFO] Building: check-tests-only/pom.xml [INFO] ..SUCCESS (2.8 s) [INFO] Building: checkstyle-goal/pom.xml [INFO] run script verify.groovy [INFO] ..SUCCESS (4.3 s) [INFO] Building: checkstyle-report/pom.xml [INFO] run script verify.groovy [INFO] ..SUCCESS (11.5 s) [INFO] Building: inlinerules/pom.xml [INFO] run script verify.groovy [INFO] ..FAILED (3.5 s) [INFO] The post-build script did not succeed. assert new File(basedir, 'target/checkstyle-checker.xml').exists() || | || false | /Users/kama/Downloads/maven-checkstyle-plugin-2.12/target/ it/inlinerules /Users/kama/Downloads/maven-checkstyle-plugin-2.12/target/ it/inlinerules/target/checkstyle-checker.xml Attached the full log file output Tested the same thing with Maven 3.1.1, Maven 3.2.1 and Maven 2.2.1 and got the same result. Sorry... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
Hi Dennis, Tested the same thing with Maven 3.1.1, Maven 3.2.1 and Maven 2.2.1 a Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: /usr/share/maven Java version: 1.7.0_21, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: mac os x, version: 10.8.5, arch: x86_64, family: mac Also on my own Build Server which runs this: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: /home/build/.jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5 Java version: 1.7.0_40, vendor: Oracle Corporation Java home: /home/build/tools/jdk1.7.0_40/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.8.0-29-generic, arch: amd64, family: unix [INFO] Error stacktraces are turned on. the same result Kind regards Karl-Heinz - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release ASF Parent POM version 14
+1 -- Olivier On Mar 7, 2014 8:19 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: Hi, Changes since the last release: http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEADr2=1434717diff_format=h Staging repo: https://repository.apache.org/content/repositories/orgapacheapache-1000/ https://repository.apache.org/content/repositories/orgapacheapache-1000/org/apache/apache/14/apache-14-source-release.zip Source release checksum: apache-14-source-release.zip sha1: 6bed0856a4cc8d9ee5f4481b8a1e0a4460076073 Staging site: http://maven.apache.org/pom-archives/asf-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
Hi Dennis, the problem was the hard coded version in the integration test inlinerules/pom.xml instead of @project.version@ Fixed in r1575711 Kind regards Karl-Heinz - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
Am 2014-03-08 23:49, schrieb Dennis Lundberg: Hi, We solved 15 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=Htmlversion=19723 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1010/ https://repository.apache.org/content/repositories/maven-1010/org/apache/maven/plugins/maven-checkstyle-plugin/2.12/maven-checkstyle-plugin-2.12-source-release.zip Source release checksum(s): maven-checkstyle-plugin-2.12-source-release.zip sha1: 1d2c6435e214daa9bedce6d32871a8b7ac3f Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote is open for 72 hours. +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Developing Maven Archetype
Hey guys,
here's an interesting question: how do you develop your maven archetypes? I
have a web-project that consists of lots of controllers and jsps, and I
have been developing this for a long time, and I want to keep developing
it. I also want to provide this project to my clients as an archetype so
they can be up-and-running as quickly as possible.
I thought of creating an archetype from my project every time I release the
archetype, but that seems really unefficient as I release new versions very
often, and also the archetype is quite complicated.
I also thought to create the archetype once, and keep developing it in
Eclipse, but that's not possible because for instance the package names
look like this:
package ${packageName};
and of-course Eclipse complains.
So my questions is - if you have a complicated archetype that you keep
developing over time, how do you develop it? Is there an Eclipse/IntelliJ
plugin for archetype developing?
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
Re: Developing Maven Archetype
Are you sure that you absolutely need parameterized Java code? There's
really no good way to work with it. You could instead use the
maven-shade-plugin to customer-ize your results as part of their
build.
On Sun, Mar 9, 2014 at 3:36 PM, Petar Tahchiev paranoia...@gmail.com wrote:
Hey guys,
here's an interesting question: how do you develop your maven archetypes? I
have a web-project that consists of lots of controllers and jsps, and I
have been developing this for a long time, and I want to keep developing
it. I also want to provide this project to my clients as an archetype so
they can be up-and-running as quickly as possible.
I thought of creating an archetype from my project every time I release the
archetype, but that seems really unefficient as I release new versions very
often, and also the archetype is quite complicated.
I also thought to create the archetype once, and keep developing it in
Eclipse, but that's not possible because for instance the package names
look like this:
package ${packageName};
and of-course Eclipse complains.
So my questions is - if you have a complicated archetype that you keep
developing over time, how do you develop it? Is there an Eclipse/IntelliJ
plugin for archetype developing?
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin / Maven default folder layout
So based on the discussion could we go with the following: /src/main * are files required during compile time (production) /src/test * are files required during test time (unit testing; based on naming schema we could also have integration tests here) /src/it * are files required during integration tests (primarily for plugins) /src/assembly * for assembly descriptors and appropriate filter property files. The /src/it/ should be added to the default folder layout page. Should we start a VOTE for this ? Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin / Maven default folder layout
Sounds good to me. /Anders On Sun, Mar 9, 2014 at 9:02 PM, Karl Heinz Marbaise khmarba...@gmx.dewrote: So based on the discussion could we go with the following: /src/main * are files required during compile time (production) /src/test * are files required during test time (unit testing; based on naming schema we could also have integration tests here) /src/it * are files required during integration tests (primarily for plugins) /src/assembly * for assembly descriptors and appropriate filter property files. The /src/it/ should be added to the default folder layout page. Should we start a VOTE for this ? Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Developing Maven Archetype
Just a quick thought, maybe using some hacky form of a development profile
using the templating-maven-plugin to filter those properties could help?
2014-03-09 20:47 GMT+01:00 Benson Margulies bimargul...@gmail.com:
Are you sure that you absolutely need parameterized Java code? There's
really no good way to work with it. You could instead use the
maven-shade-plugin to customer-ize your results as part of their
build.
On Sun, Mar 9, 2014 at 3:36 PM, Petar Tahchiev paranoia...@gmail.com
wrote:
Hey guys,
here's an interesting question: how do you develop your maven
archetypes? I
have a web-project that consists of lots of controllers and jsps, and I
have been developing this for a long time, and I want to keep developing
it. I also want to provide this project to my clients as an archetype so
they can be up-and-running as quickly as possible.
I thought of creating an archetype from my project every time I release
the
archetype, but that seems really unefficient as I release new versions
very
often, and also the archetype is quite complicated.
I also thought to create the archetype once, and keep developing it in
Eclipse, but that's not possible because for instance the package names
look like this:
package ${packageName};
and of-course Eclipse complains.
So my questions is - if you have a complicated archetype that you keep
developing over time, how do you develop it? Is there an Eclipse/IntelliJ
plugin for archetype developing?
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: Developing Maven Archetype
Hello,
thanks for your responses. Yes, unforutnately, I do need parameterized Java
code (package names, classnames, also xml files, etc..). As I said it's
pretty complicated project.
I looked at templating-maven-plugin but it seems that filtering the
standard src/main/java folder is not supported. Also, I may not understand
the quite your suggestion, but using the templating-maven-plugin will also
break Eclipse as I will be still having ${packageName} in my sources.
I'm kind of surprised that no one else has had this problem before. Does
this mean that the archetypes are only supposed to work with simple
projects that are not continuously developed?
2014-03-09 22:50 GMT+02:00 Baptiste Mathus bmat...@batmat.net:
Just a quick thought, maybe using some hacky form of a development profile
using the templating-maven-plugin to filter those properties could help?
2014-03-09 20:47 GMT+01:00 Benson Margulies bimargul...@gmail.com:
Are you sure that you absolutely need parameterized Java code? There's
really no good way to work with it. You could instead use the
maven-shade-plugin to customer-ize your results as part of their
build.
On Sun, Mar 9, 2014 at 3:36 PM, Petar Tahchiev paranoia...@gmail.com
wrote:
Hey guys,
here's an interesting question: how do you develop your maven
archetypes? I
have a web-project that consists of lots of controllers and jsps, and I
have been developing this for a long time, and I want to keep
developing
it. I also want to provide this project to my clients as an archetype
so
they can be up-and-running as quickly as possible.
I thought of creating an archetype from my project every time I release
the
archetype, but that seems really unefficient as I release new versions
very
often, and also the archetype is quite complicated.
I also thought to create the archetype once, and keep developing it in
Eclipse, but that's not possible because for instance the package names
look like this:
package ${packageName};
and of-course Eclipse complains.
So my questions is - if you have a complicated archetype that you keep
developing over time, how do you develop it? Is there an
Eclipse/IntelliJ
plugin for archetype developing?
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
Re: [VOTE] Release Apache Maven Filtering version 1.2
Hi, The vote has passed with the following result: +1 (binding): Robert Scholte, Hervé BOUTEMY, Mark Struberg +1 (non binding): Karl Heinz Marbaise I will promote the artifacts to the central repo. Robert Op Thu, 06 Mar 2014 22:08:10 +0100 schreef Robert Scholte rfscho...@apache.org: Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=18729styleName=Html There is still 1 issue left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11761status=1component=13380 Staging repo: https://repository.apache.org/content/repositories/maven-1009/ https://repository.apache.org/content/repositories/maven-1009/org/apache/maven/shared/maven-filtering/1.2/maven-filtering-1.2-source-release.zip Source release checksum(s): maven-filtering-1.2-source-release.zip sha1: 50185091c5be24ee3a01296224d9d4eee77852c9 Staging site: http://maven.apache.org/shared-archives/maven-filtering-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 thanks, Robert - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Developing Maven Archetype
Well, IMO an archetype is by definition something rarely used: you often
work on an existing project, but are unlikely to create a new one every day.
So, you may have a very specific use-case, and that is often the cause of
something not working the way one want on a specific situation.
I was talking about templating-m-p in Eclipse because I thought you may
somehow be able to use the m2e.version property to activate a special dev
profile that would for example define your archetype sources as the source
for filtering, re/define some kind of hardcoded dev properties and so on to
be able to iterate inside the IDE. Not that clean, sounding a bit hacky as
I said, but may seem acceptable since it's only for use when the project is
open in the IDE.
You also have to develop your archetype's ITs to ensure it keeps working
[1]. But I suppose you already do so.
Cheers
-- Baptiste
[1]
https://maven.apache.org/archetype/maven-archetype-plugin/integration-test-mojo.html
2014-03-09 22:06 GMT+01:00 Petar Tahchiev paranoia...@gmail.com:
Hello,
thanks for your responses. Yes, unforutnately, I do need parameterized Java
code (package names, classnames, also xml files, etc..). As I said it's
pretty complicated project.
I looked at templating-maven-plugin but it seems that filtering the
standard src/main/java folder is not supported. Also, I may not understand
the quite your suggestion, but using the templating-maven-plugin will also
break Eclipse as I will be still having ${packageName} in my sources.
I'm kind of surprised that no one else has had this problem before. Does
this mean that the archetypes are only supposed to work with simple
projects that are not continuously developed?
2014-03-09 22:50 GMT+02:00 Baptiste Mathus bmat...@batmat.net:
Just a quick thought, maybe using some hacky form of a development
profile
using the templating-maven-plugin to filter those properties could help?
2014-03-09 20:47 GMT+01:00 Benson Margulies bimargul...@gmail.com:
Are you sure that you absolutely need parameterized Java code? There's
really no good way to work with it. You could instead use the
maven-shade-plugin to customer-ize your results as part of their
build.
On Sun, Mar 9, 2014 at 3:36 PM, Petar Tahchiev paranoia...@gmail.com
wrote:
Hey guys,
here's an interesting question: how do you develop your maven
archetypes? I
have a web-project that consists of lots of controllers and jsps,
and I
have been developing this for a long time, and I want to keep
developing
it. I also want to provide this project to my clients as an archetype
so
they can be up-and-running as quickly as possible.
I thought of creating an archetype from my project every time I
release
the
archetype, but that seems really unefficient as I release new
versions
very
often, and also the archetype is quite complicated.
I also thought to create the archetype once, and keep developing it
in
Eclipse, but that's not possible because for instance the package
names
look like this:
package ${packageName};
and of-course Eclipse complains.
So my questions is - if you have a complicated archetype that you
keep
developing over time, how do you develop it? Is there an
Eclipse/IntelliJ
plugin for archetype developing?
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: maven-assembly-plugin / Maven default folder layout
Am 2014-03-09 21:02, schrieb Karl Heinz Marbaise: So based on the discussion could we go with the following: /src/main * are files required during compile time (production) /src/test * are files required during test time (unit testing; based on naming schema we could also have integration tests here) /src/it * are files required during integration tests (primarily for plugins) /src/assembly * for assembly descriptors and appropriate filter property files. The /src/it/ should be added to the default folder layout page. +1 You forgot: src/site. Always use a relative path in the docs otherwise it could be misinterpreted. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Developing Maven Archetype
Generate the archetype from your working source.
Sent from my iPhone
On 10/03/2014, at 8:06 AM, Petar Tahchiev paranoia...@gmail.com wrote:
Hello,
thanks for your responses. Yes, unforutnately, I do need parameterized Java
code (package names, classnames, also xml files, etc..). As I said it's
pretty complicated project.
I looked at templating-maven-plugin but it seems that filtering the
standard src/main/java folder is not supported. Also, I may not understand
the quite your suggestion, but using the templating-maven-plugin will also
break Eclipse as I will be still having ${packageName} in my sources.
I'm kind of surprised that no one else has had this problem before. Does
this mean that the archetypes are only supposed to work with simple
projects that are not continuously developed?
2014-03-09 22:50 GMT+02:00 Baptiste Mathus bmat...@batmat.net:
Just a quick thought, maybe using some hacky form of a development profile
using the templating-maven-plugin to filter those properties could help?
2014-03-09 20:47 GMT+01:00 Benson Margulies bimargul...@gmail.com:
Are you sure that you absolutely need parameterized Java code? There's
really no good way to work with it. You could instead use the
maven-shade-plugin to customer-ize your results as part of their
build.
On Sun, Mar 9, 2014 at 3:36 PM, Petar Tahchiev paranoia...@gmail.com
wrote:
Hey guys,
here's an interesting question: how do you develop your maven
archetypes? I
have a web-project that consists of lots of controllers and jsps, and I
have been developing this for a long time, and I want to keep
developing
it. I also want to provide this project to my clients as an archetype
so
they can be up-and-running as quickly as possible.
I thought of creating an archetype from my project every time I release
the
archetype, but that seems really unefficient as I release new versions
very
often, and also the archetype is quite complicated.
I also thought to create the archetype once, and keep developing it in
Eclipse, but that's not possible because for instance the package names
look like this:
package ${packageName};
and of-course Eclipse complains.
So my questions is - if you have a complicated archetype that you keep
developing over time, how do you develop it? Is there an
Eclipse/IntelliJ
plugin for archetype developing?
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release ASF Parent POM version 14
+1 Le jeudi 6 mars 2014 22:18:56 Hervé BOUTEMY a écrit : Hi, Changes since the last release: http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEADr2=143 4717diff_format=h Staging repo: https://repository.apache.org/content/repositories/orgapacheapache-1000/ https://repository.apache.org/content/repositories/orgapacheapache-1000/org/ apache/apache/14/apache-14-source-release.zip Source release checksum: apache-14-source-release.zip sha1: 6bed0856a4cc8d9ee5f4481b8a1e0a4460076073 Staging site: http://maven.apache.org/pom-archives/asf-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release ASF Parent POM version 14
Hi, The vote has passed with the following result: +1 (binding): Benson Margulies, Stephen Connolly, Jason van Zyl, Daniel Kulp,Kristian Rosenvold, Olivier Lamy, Karl-Heinz Marbaise, Robert Scholte, Mark Struberg, Hervé Boutemy +1 (non binding): Tony Chemit I will promote the artifacts to the central repo.
