you can set it in cli,
-Dappserver.base=C:\EclipsePack\continuum\trunk\continuum-webapp\target
^_^
Christophe LECHENNE wrote:
Hi all,
After a successful build, when I try to start continuum as it's written in README.txt, I've got :
java.io.FileNotFoundException:
C:\EclipsePack\continuum\t
They definitely should be integration tests, not unit tests. Something as
time-consuming as a maven build shouldn't really be used during unit
testing. In the case of the eclipse plugin, the fact that it was running
these builds during unit testing causes the issue where the testing version
of the
OK, what I found was this:
1. the reason the eclipse plugin had this problem was that it was running
these test builds (including staging the plugin) during the unit-test phase,
before the plugin was packaged or the plugin-jar assigned to the project
artifact. Technically, this use case should be
Hmm, that won't quite work, though, since it'll kill the test local
repo...I'll work on it some more.
-john
On 12/20/06, John Casey <[EMAIL PROTECTED]> wrote:
Ah, right, ok...forgot about that point.
I've added code to run a 'clean' build after the plugin is staged.
On 12/20/06, Barrie Trelo
Ah, right, ok...forgot about that point.
I've added code to run a 'clean' build after the plugin is staged.
On 12/20/06, Barrie Treloar <[EMAIL PROTECTED]> wrote:
I've listed the problems in the JIRA entry and started a new thread
for this discussion.
The problem is that the ProjectTools end
I've listed the problems in the JIRA entry and started a new thread
for this discussion.
The problem is that the ProjectTools end up invoking another maven
with mangled information and that this causes target/classes to have a
junk plugin.xml which is then used in the jar phase.
On 12/21/06, Joh
are you sure it wasn't just a case of the IT-staging process somehow hitting
the deploy phase of the build? That would've done it.
The ITs currently use the maven-invoker, which forks an entirely new Maven
process, both for building the test version of the plugin, and for running
each test build.
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (20 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-1273please upload Oracle JDBC drivers POMs to maven repo
http://jira.codehaus.org/browse/MAVENUPLOAD-1273
MAVENUPLOAD-1275Upload UmlGraph 4.5
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (37 issues)
Subscriber: mavendevlist
Key Summary
MEV-457 Geronimo jar fails to download
http://jira.codehaus.org/browse/MEV-457
MEV-352 Relocate cvslib in netbeans groupId to cvsclient in org.net
Christophe LECHENNE a écrit :
Hi all,
After a successful build, when I try to start continuum as it's written in README.txt, I've got :
java.io.FileNotFoundException:
C:\EclipsePack\continuum\trunk\continuum-webapp\target\logs\continuum.log (Le
chemin d'accès spécifié est introuvable)
See http://jira.codehaus.org/browse/MECLIPSE-192
maven-plugin-testing-tools builds the test jar by mangling the pom
info to include the test version and then run BuiltTool.executeMaven()
with the "package" phase to create the test jar.
The side effect of this is to put test artifacts into
D:\ide
Mangling occurs in ProjecTool.packageProjectArtifact().
This mangles the pom info to include the test version and then run
BuiltTool.executeMaven() with the "package" phase to create the test
jar. The side effect of this is to put test artifacts into
D:\ide\workspace\maven\maven-eclipse-plugin\ta
Hi all,
After a successful build, when I try to start continuum as it's written in
README.txt, I've got :
java.io.FileNotFoundException:
C:\EclipsePack\continuum\trunk\continuum-webapp\target\logs\continuum.log (Le
chemin d'accès spécifié est introuvable) .
2006-12-19 22:08:50.468::WARN:
On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
Jason van Zyl wrote:
>
> On 19 Dec 06, at 12:28 PM 19 Dec 06, Steve Loughran wrote:
>
>> Jason van Zyl wrote:
>>> Hi,
>>> Just checking in with folks to see if anyone is planning ApacheCon
>>> talks.
>>
>> 1. "fear the repository police". We
On 12/20/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
just some holiday fun ahead...
On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
> >> We are
> >>
> >> 1. planning an apache con EU talk, "fear the repository police".
> >
> > in suitable costumes, i hope ;-)
>
> nothing planned, but if
On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> robert burrell donkin wrote:
>> > On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> 2. looking to get management approval to hand the code t
See http://jira.codehaus.org/browse/MECLIPSE-192
From the jira comments:
In AbstractJarMojo.java line 152:
archiver.getArchiver().addDirectory( contentDirectory,
DEFAULT_INCLUDES, DEFAULT_EXCLUDES );
where
contentDirectory = D:\ide\workspace\maven\maven-eclipse-plugin\target\classes
This di
not sure what went wrong, but look at these:
http://www.nabble.com/Maven-eclipse-plugin-error-tf2692962.html#a7509615
http://jira.codehaus.org/browse/MECLIPSE-192
I'm still investigating why this occurs.
I think it is either the stuff in maven-plugin-testing-tools is
mangling something it shoul
On 12/20/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
On Wed, December 20, 2006 1:27 pm, Steve Loughran wrote:
> "who is interested in working with me to come up with something that is
> broadly useful"?
>
> One troublespot with proxy code is testing. I know I cant test NTLM
> proxies, but do a
FWIW, I just added code to the maven-plugin-testing-tools that will override
the distributionManagement section in the test POM, making deployment of the
plugin using the altered version impossible.
On 12/20/06, John Casey <[EMAIL PROTECTED]> wrote:
There are two things you need to test, right?
just some holiday fun ahead...
On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> We are
>>
>> 1. planning an apache con EU talk, "fear the repository police".
>
> in suitable costumes, i hope ;-)
nothing planned, but if we have someone in the audience cued up to say
"I didnt expect the
I agree, having an alpha will only help with more eyes looking into it
On 12/20/06, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
Jason van Zyl wrote:
>
> On 19 Dec 06, at 4:31 PM 19 Dec 06, Brett Porter wrote:
>
>> Hi,
>>
>> I am going to start looking into the issue with Archiva hanging on
>> repo
There are two things you need to test, right?
1. unit test functionality within the plugin, to make sure that
subcomponents and classes within the implementation are functioning
correctly
2. integration test functionality that depends on Maven (the runtime
context) to produce results. This is wh
On 12/20/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
There was support in maven to run plugins from target/, but it was broken:
MNG-2677 (originally MNG-870).
well, the eclipse plugin was using that till a few weeks ago and I can
assure it was working!
I was able to modify the plugin code f
Fabrizio Giustina wrote:
Hi John,
On 12/20/06, John Casey <[EMAIL PROTECTED]> wrote:
I switched to using a testing version of the plugin (which BTW is only
resolvable ever in the repo created during the integration testing
phase) so
the ITs themselves wouldn't have to:
a. adjust to new plu
Hi,
Vote results: 4 bindings (Fabrizio, Jason, Jesse, Stephane), 1 non
binding (Rahul).
Jason will help for the maven ear 2.3 release. I'll keep you posted
once it's done.
Cheers,
Stéphane
On 12/16/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
Hi,
I'd like to release maven-ear-plugin 2.3 [1
Hi John,
On 12/20/06, John Casey <[EMAIL PROTECTED]> wrote:
I switched to using a testing version of the plugin (which BTW is only
resolvable ever in the repo created during the integration testing phase) so
the ITs themselves wouldn't have to:
a. adjust to new plugin versions in order to run
b
On 12/20/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
John Casey wrote:
> Hmm, okay. I'm just going to reply at the top level, since I'm going to
> make
> a few general comments:
>
> 1. I really like this explanation/algorithm/implementation. It seems to
> take
> into account a LOT of permu
Well, I'm certainly not an expert on the RPM versioning stuff, yet. I'll be
studying it intensely in the near future, and then I'll put something
together (for my own notes, if nothing else...so I'll be happy to share).
As far as splitting the discussion, I agree, except for one point: we need
to
John Casey wrote:
Hmm, okay. I'm just going to reply at the top level, since I'm going to
make
a few general comments:
1. I really like this explanation/algorithm/implementation. It seems to
take
into account a LOT of permutations, and even more importantly, it specifies
a specification tha
I switched to using a testing version of the plugin (which BTW is only
resolvable ever in the repo created during the integration testing phase) so
the ITs themselves wouldn't have to:
a. adjust to new plugin versions in order to run
b. rely on metadata resolution for the plugin version, which ca
+1
On 12/16/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
Dependencies used by the maven-eclipse-plugin have been released and a
stable revision for a vote has been set.
I'd like to restart a vote based on:
- svn rev. 487861
- snapshot deployed at
http://people.apache.org/repo/m2-snapshot-
Hmm, okay. I'm just going to reply at the top level, since I'm going to make
a few general comments:
1. I really like this explanation/algorithm/implementation. It seems to take
into account a LOT of permutations, and even more importantly, it specifies
a specification that we can write down in w
Hi all,
I have been trying to investigate how practical it is to build eclipse
plugins using maven, and have run into some conceptual issues which are
not explained at all in any of the docs I have found.
So far, the pde-maven-plugin shows the most promise in building an eclipse
rcp application.
I'd be fine with that too, but in this thread people was complaining
about standardizing other's people versions that don't use dots or are
more complex
On 12/20/06, Max Bowsher <[EMAIL PROTECTED]> wrote:
Carlos Sanchez wrote:
> I'd just prefer have xml syntax over string parsing and encourage
>
On 20 Dec 06, at 6:32 AM 20 Dec 06, Fabrizio Giustina wrote:
The vote has ended, with 5 positive votes from PMC members. The maven
eclipse plugin will be released with version 2.3.
Jason, I will leave the actual release to you as discussed, you can
now proceed.
Great I can take care of t
FYI, the issue w/ TestNG and Surefire is here:
http://jira.opensymphony.com/browse/TESTNG-122
I dont like the look of one of the patches, but the other seems to be
the changes to surefire testng support to keep it in sync w/ testng 5.2+
Perhaps when the maven support on gump goes live, the t
Jason van Zyl wrote:
On 19 Dec 06, at 12:28 PM 19 Dec 06, Steve Loughran wrote:
Jason van Zyl wrote:
Hi,
Just checking in with folks to see if anyone is planning ApacheCon
talks.
1. "fear the repository police". We will pick people in the audience
and beat them with rolled up copies of th
robert burrell donkin wrote:
On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>
>
>
>> I'd like to see POM auditing in there somewhere.
>
> +1
>
> henri's been talking about adding this to RAT. IMHO this
Carlos Sanchez wrote:
> I'd just prefer have xml syntax over string parsing and encourage
> people to use whatever the standard we choose.
Whilst in general, XML can be useful, this might be overusing it.
Versions *must* have some sort of string representation, to be embedded
in file names. That
On Wed, December 20, 2006 1:27 pm, Steve Loughran wrote:
> "who is interested in working with me to come up with something that is
> broadly useful"?
>
> One troublespot with proxy code is testing. I know I cant test NTLM
> proxies, but do at least have access to an unauthenticated proxy-whether
>
The vote has ended, with 5 positive votes from PMC members. The maven
eclipse plugin will be released with version 2.3.
Jason, I will leave the actual release to you as discussed, you can now proceed.
(about the way the plugin is tested: I totally agree that installing a
test version into the l
Brett Porter wrote:
On 19/12/2006, at 9:39 PM, Steve Loughran wrote:
Anyone interested in working on this?
Thanks for volunteering! :)
I knew that would happen. But I suspect that nobody else would do it.
How about,
"who is interested in working with me to come up with something that is
Dennis Lundberg wrote:
Jason van Zyl wrote:
On 19 Dec 06, at 12:28 PM 19 Dec 06, Steve Loughran wrote:
Jason van Zyl wrote:
Hi,
Just checking in with folks to see if anyone is planning ApacheCon
talks.
1. "fear the repository police". We will pick people in the audience
and beat them wit
Hi Kenney
On 12/19/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
> The vote for the release of the eclipse plugin (and related shared ...
I also voted, btw (on the 2nd try).
this mail was sent before the restart of the vote, I will send a new
vote result for the "second try" thread soon.
>
Dennis Lundberg wrote:
Jason van Zyl wrote:
On 19 Dec 06, at 12:28 PM 19 Dec 06, Steve Loughran wrote:
Jason van Zyl wrote:
Hi,
Just checking in with folks to see if anyone is planning ApacheCon
talks.
1. "fear the repository police". We will pick people in the audience
and beat them wit
46 matches
Mail list logo
