I'm doing a whole series of releases at the moment for supporting
multithreaded builds (and some bugs related to that), and anything
that's not already fixed (with
decent test-cases) I'm just ignoring. As I announced a week ago
(http://www.mail-archive.com/dev@maven.apache.org/msg84663.html), th
On 18 May 2010 06:52, Ludwig Magnusson wrote:
> I don't have an official say in this but I recently submitted a patch for
> an
> issue I created that allows for a "skip" parameter to the install plugin. I
> assigned it to the 2.4 version (2.3.1 did not exist in jira at the time).
> Is
>
FYI, If
I don't have an official say in this but I recently submitted a patch for an
issue I created that allows for a "skip" parameter to the install plugin. I
assigned it to the 2.4 version (2.3.1 did not exist in jira at the time). Is
it possible to add this patch or is it too much work?
Check it out he
Hi all,
Can any one help me I am getting the following error
install:
[artifact:pom] An error has occurred while processing the Maven artifact
tasks.
[artifact:pom] Diagnosis:
[artifact:pom]
[artifact:pom] Error building POM (may not be this project's POM).
[artifact:pom]
[artifact:pom]
[art
In m3 if you activate the // mode and you have a plugin which isn't marked as
compatible you'll have a warning like that :
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains t
I actually want to recommend something more formal inside of Maven. It
seems that some kind of rule should exist to force a minimum version.
Paul
2010/5/17 Martin Gainty :
>
> Hi Paul
>
>
>
> would a custom rule work?
> http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html
>
>
Hi Paul
would a custom rule work?
http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html
?
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten S
Lots of plugins are up for vote to be @threadSafe with Maven 3. Does
Maven 3 have any mechanism to reject plugins prior to the versions
being released? What happens if someone uses a Maven 2 version?
Paul
-
To unsubscribe, e-mail
+1
On 17 May 2010 22:27, Benjamin Bentmann wrote:
> Hi,
>
> We solved 1 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11147&version=16467
> 1
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11147&s
+1
On 17 May 2010 23:59, Kristian Rosenvold wrote:
> Hi,
>
> We solved 1 issue:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11130&version=16462
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQ
+1
On 17 May 2010 23:58, Kristian Rosenvold wrote:
> Hi,
>
> We solved 1 issue:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145&version=16471
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQ
+1
On 17 May 2010 23:58, Kristian Rosenvold wrote:
> Hi,
>
> We solved 1 issue:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11136&version=16459
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQ
+1
On 17 May 2010 23:58, Kristian Rosenvold wrote:
> Hi,
>
> We solved 2 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&version=16465
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jql
+1
On 17 May 2010 23:58, Kristian Rosenvold wrote:
> Hi,
>
> We solved 2 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=16491
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jql
Hi,
We solved 1 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11147&version=16467
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11147&status=1
Staging repo:
https://repository.apache.org/content/repositor
Hi,
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11130&version=16462
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MCOMPILER+AND+resolution+%3D+Unresolved+ORDER+BY+up
Hi,
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145&version=16471
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MRESOURCES+AND+resolution+%3D+Unresolved+ORDER+BY+up
Hi,
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11136&version=16459
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MINSTALL+AND+resolution+%3D+Unresolved+ORDER+BY+upda
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&version=16465
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MEAR+AND+resolution+%3D+Unresolved+ORDER+BY+update
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=16491
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MJAR+AND+resolution+%3D+Unresolved+ORDER+BY+update
The grid had been left using the plugin-enforcer to tie the surefire version
down to 2.4
For this build Benjamin changed maven back to stock 2.2.1
3.0-beta-1 works on my machines, but we (not me but somebody who works for
sonatype) should add it to the grid
-Stephen
On 17 May 2010 15:56, Hu
Haroon Rafique wrote:
Anything else I can do? Sample project with POM in a JIRA?
Thanks but we already have an integration test for the related issue
MNG-3530.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apac
On Today at 4:19pm, BB=>Benjamin Bentmann wrote:
BB> Haroon Rafique wrote:
BB>
BB> >
BB> >
BB> > src/main/resources
BB> > ../${app.key}
BB> > true
BB> >
BB> >
BB> >[...]
BB> > a) maven-3.0-beta-1
BB> > b) properties-maven-plugin in conjunction with maven-3.0-beta-1
BB>
BB> This setup requir
Haroon Rafique wrote:
src/main/resources
../${app.key}
true
[...]
a) maven-3.0-beta-1
b) properties-maven-plugin in conjunction with maven-3.0-beta-1
This setup requires a questionable feature [0] to work. Questionable
because it decreases performance but serves only few use cases. It's n
//did you try setting the necessary properties in settings.xml or profiles.xml
e.g.?
appserverConfig
1.0
appserverConfig
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Martin Gainty
__
Congratulations Paul !
Arnaud
On May 14, 2010, at 11:34 PM, Brian Fox wrote:
> The Maven PMC recently voted to invite Paul Gier to join us as a
> member of the PMC Committee. He accepted and is now officially part of
> the Maven PMC. Congratulations Paul!
>
> If you'd like to read more about wh
No worries... though I need to call a vote to get a 3.0-beta-1 compatible
version published
2010/5/17 Benjamin Bentmann
> Barışcan Güngör wrote:
>
> [...] we
>>
>> could specify a variable for the application version in the parent pom, so
>> that
>> in the child poms we could able to specify th
+1
Arnaud
On May 16, 2010, at 3:34 PM, Benjamin Bentmann wrote:
> Hi,
>
> We solved 2 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&version=16314
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pi
Barışcan Güngör wrote:
[...] we
could specify a variable for the application version in the parent pom, so that
in the child poms we could able to specify the version by the same variable.
That helps us saving our time for updating version number in each project
upgrade and for reusability.
Oh
You were relying on a bug.
the following xpath:/project/parent/groupId,
xpath:/project/parent/artifactId, xpath:/project/parent/version,
xpath:/project/groupId, xpath:/project/artifactId, xpath:/project/version
cannot ever reference a property as they are all evaluated before the model
is availabl
Barışcan Güngör wrote:
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”.
A POM deployed to a repository must be self-contained in the way that
all information required to process it (e.g. calculate the effective
POM) mus
Everything passed on my machine before I committed the change... I'll re-run
again
On 17 May 2010 14:48, Stephen Connolly wrote:
> Balls!
>
> FYI, I'm looking into this
>
> -Stephen
>
>
> On 17 May 2010 14:40, Hudson wrote:
>
>> See <
>> http://grid.sonatype.org/ci/job/surefire/./jdk=1.5,label=u
Balls!
FYI, I'm looking into this
-Stephen
On 17 May 2010 14:40, Hudson wrote:
> See <
> http://grid.sonatype.org/ci/job/surefire/./jdk=1.5,label=ubuntu/61/changes
> >
>
> Changes:
>
> [stephenc] [SUREFIRE-592] Tidy-up poms
>
> o Removing unused dependencies
>
> [stephenc] [SUREFIRE-592] Parti
Hello, all.
I'm not sure it's a proper place for this question. Please redirect
me if it's not.
Does anybody know, if it's possible to get the path to the .pom file
accompanying installed primary project artifacts from the Maven API?
My current solution is to replace the extension of a primary a
Hi,
At first, thanks for your attention and time to read.
In our enterprise applications we use MyEclipse 8.5 with
M2Eclipse maven3 plug-in support. Before begining to use maven3, with maven2 we
could specify a variable for the application version in the parent pom, so that
in the child
Consider the following project:
P1
m1
m2
m2.1
m2.2
m3
m3.1
m3.2
m3.3
--- pom.xml
For testing, mocking, prototyping... we often want to be able to replace a
set of modules/artifacts by new modules/artifacts: for inst
+1
On 17 May 2010 08:10, Olivier Lamy wrote:
> +1
>
> 2010/5/16 Benjamin Bentmann :
> > Hi,
> >
> > We solved 2 issues:
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&version=16314
> >
> > There are still a couple of issues left in JIRA:
> >
> http://jira.codehaus.org/sec
+1
2010/5/16 Benjamin Bentmann :
> Hi,
>
> We solved 2 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&version=16314
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11540&status=1
>
> Staging repo:
+1
/Paul
Le dimanche 16 mai 2010 15:34:01, Benjamin Bentmann a écrit :
> Hi,
>
> We solved 2 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&version=16
> 314
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?res
39 matches
Mail list logo
