just for information, before someone asks: I know I broke one Jenkins job when
hoping to fix another one...
I'll continue my tests tonight to fix these jobs *at the same time* :)
Regards,
Herve
Le dimanche 9 mars 2014 19:43:48 hbout...@apache.org a écrit :
> Repository: maven-integration-testi
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
+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=HEAD&r2=143
> 4717&diff_format=h
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheapache-1000/
> ht
Generate the archetype from your working source.
Sent from my iPhone
On 10/03/2014, at 8:06 AM, Petar Tahchiev 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 comp
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 integrati
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 talk
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
:
Hi,
We solved 5 issues
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.
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 :
> Are you sure that you absolutely need parameterized Java code? There's
> really no good way to work
Sounds good to me.
/Anders
On Sun, Mar 9, 2014 at 9:02 PM, Karl Heinz Marbaise wrote:
> 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; bas
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 dur
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 wrote:
> Hey guys,
>
> here's an interesting
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 archety
Am 2014-03-08 23:49, schrieb Dennis Lundberg:
Hi,
We solved 15 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&styleName=Html&version=19723
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11127&status=1
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
Fo
+1
--
Olivier
On Mar 7, 2014 8:19 AM, "Hervé BOUTEMY" wrote:
> Hi,
>
> Changes since the last release:
>
> http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEAD&r2=1434717&diff_format=h
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheapache-1000/
>
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/JavaVirtualMach
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" :
> Hi,
>
> unfortunately i have to retire my +1 cause i found an issue in the
> integration tests (i was to fast with the se
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-che
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?pro
+1
LieGrue,
strub
> On Saturday, 8 March 2014, 17:13, Hervé BOUTEMY 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=11761&version=187
>> 29
+1
LieGrue,
strub
> On Thursday, 6 March 2014, 22:19, Hervé BOUTEMY wrote:
> > Hi,
>
> Changes since the last release:
> http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEAD&r2=1434717&diff_format=h
>
> Staging repo:
> https://repository.apache.org/content/repositories/o
+1
Op Thu, 06 Mar 2014 22:18:56 +0100 schreef Hervé BOUTEMY
:
Hi,
Changes since the last release:
http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEAD&r2=1434717&diff_format=h
Staging repo:
https://repository.apache.org/content/repositories/orgapacheapache-1000/
https://re
+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=11127&styleName=H
> tml&version=19723
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/Is
+1
and thanks for pushing this, Dennis!
LieGrue,
strub
> On Saturday, 8 March 2014, 23:50, Dennis Lundberg wrote:
> > Hi,
>
> We solved 15 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&styleName=Html&version=19723
>
> There are still a couple of issues left i
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
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
27 matches
Mail list logo