+1, if what you're looking for is essentially classpath isolation
management, then ClassWorlds is one way to go.
Btw, I think you might find many examples in different maven plugins.
My 2 cents
2014-02-08 19:04 GMT+01:00 Jason van Zyl ja...@takari.io:
On Feb 8, 2014, at 12:42 PM, Benson
no problem to delete mine
maven-assembly-plugin-2.0.x
On Mon, Feb 10, 2014 at 12:17 AM, Karl Heinz Marbaise khmarba...@gmx.dewrote:
Hi,
i would like to suggest to remove some branches in the following area:
https://svn.apache.org/repos/asf/maven/plugins/branches
I would like to delete
Hi,
done in r1566721
Kind regards
Karl Heinz Marbaise
Hi,
i would like to suggest to remove some branches in the following area:
https://svn.apache.org/repos/asf/maven/plugins/branches
I would like to delete the following branches, cause they are really old:
MASSEMBLY-128/
MASSEMBLY-14/
Just running through some final tests, if no one has any objections I will
stage the 3.2.0 later today.
On Feb 8, 2014, at 3:32 PM, Robert Scholte rfscho...@apache.org wrote:
Done.
Robert
Op Sat, 08 Feb 2014 18:07:54 +0100 schreef Jason van Zyl ja...@takari.io:
Sure, no problem. I'm
I understand the value of core ITs and fear about such changes
I both think such a change has a value to keep existing ITs written a long
time ago easier for newcomers to understand
But yes, I see my update wasn't careful enough
In the next days, I'll check that generated plugin.xml is exactly
So the current setup of the RAT plugin let me tag everything and then it blew
up while trying to build the binaries for staging. Less than ideal, surprised
me, and moderately annoying. It is never a good idea to only execute something
during a release. Absolutely guaranteed to only blow while
On Feb 10, 2014, at 7:07 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
I understand the value of core ITs and fear about such changes
I both think such a change has a value to keep existing ITs written a long
time ago easier for newcomers to understand
But yes, I see my update wasn't
If you can wait til tomorrow I'll sort it out...
On Tuesday, 11 February 2014, Jason van Zyl ja...@takari.io wrote:
So the current setup of the RAT plugin let me tag everything and then it
blew up while trying to build the binaries for staging. Less than ideal,
surprised me, and moderately
the gist says: See RAT report in:
/Users/jvanzyl/js/tesla/maven/target/checkout/maven-core/target/rat.txt
And this file says:
Unapproved licenses:
src/site/xdoc/maven-deps.odg
So I simply exclude *.odg files and add a missing license header in an
other file:
Thanks, I'll try it again.
If the setup can be on by default that would be much more helpful.
On Feb 10, 2014, at 7:38 PM, Olivier Lamy ol...@apache.org wrote:
the gist says: See RAT report in:
/Users/jvanzyl/js/tesla/maven/target/checkout/maven-core/target/rat.txt
And this file says:
GitHub user ericdahl opened a pull request:
https://github.com/apache/maven-surefire/pull/32
Fix typos and grammatical errors
I've been having some issues with my JDK and encountered the following
message while building:
```
[ERROR] Failed to execute goal
+1
On Feb 8, 2014, at 1:02 AM, Igor Fedorenko i...@ifedorenko.com wrote:
Hi,
We solved 2 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=20031
There are still a couple of issues left in JIRA:
Hi,
Time to release Maven 3.2.0!
Here is a link to Jira with 33 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15565
Staging repo:
https://repository.apache.org/content/repositories/maven-1005/
The distributable binaries and sources for testing can be
+1
---
Analyzer...
stagingUrl: https://repository.apache.org/content/repositories/maven-1005
groupId: org.apache.maven
artifactId: apache-maven
version: 3.2.0
Source ZIP url exists.
All important m2e tests pass, +1.
--
Regards,
Igor
On 2/10/2014, 21:18, Jason van Zyl wrote:
Hi,
Time to release Maven 3.2.0!
Here is a link to Jira with 33 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15565
Staging repo:
+1
But I do have a question: should we not somehow make sure new
features/improvements are well documented?
e.g. I could at least not find any docu about these:
- https://jira.codehaus.org/browse/MNG-5576
- https://jira.codehaus.org/browse/MNG-3526
- https://jira.codehaus.org/browse/MNG-5581
I
+1 to Barrie's note.
On Mon, Feb 10, 2014 at 9:55 AM, Barrie Treloar baerr...@gmail.com wrote:
On 10 February 2014 14:50, jieryn jie...@gmail.com wrote:
Don't mess with existing tests. It's always wrong to do it. You're
lazy and stupid if you do it.
Can you chill with the attitude.
Hi.
I didn't yet tested it and didn't follow dev threads but I'm really happy to
see maven going forward and proposing a little but useful new set of new
features. Like domi I would like to know if there are already some
documentation and especially about the compatibility to use these
18 matches
Mail list logo