Hi Hervé,
On 24/09/16 23:03, Hervé BOUTEMY wrote:
Le samedi 24 septembre 2016 21:37:06 Karl Heinz Marbaise a écrit :
Hi,
we have retired the maven-eclipse-plugin but we have it currently in our
plugins-trunk:
https://svn.apache.org/repos/asf/maven/plugins/trunk
what about moving it to
Le samedi 24 septembre 2016 21:37:06 Karl Heinz Marbaise a écrit :
> Hi,
>
> we have retired the maven-eclipse-plugin but we have it currently in our
> plugins-trunk:
>
> https://svn.apache.org/repos/asf/maven/plugins/trunk
>
> what about moving it to:
>
> ht
Hi,
we have retired the maven-eclipse-plugin but we have it currently in our
plugins-trunk:
https://svn.apache.org/repos/asf/maven/plugins/trunk
what about moving it to:
https://svn.apache.org/repos/asf/maven/retired/
so we don't need to build it all the time and do the checkout on Je
ented on MECLIPSE-295:
That's really cool. I would be interested in seeing more graphs of
different information you pull from these logs.
http://www.jointpainreliefcodes-review.com
http://www.yogaburn-reviews.com
Eclipse plugin fails due to missing
org.apache.maven.plugins:mav
//www.jointpainreliefcodes-review.com
http://www.yogaburn-reviews.com
Eclipse plugin fails due to missing
org.apache.maven.plugins:maven-eclipse-plugin:pom:test
--
Key: MECLIPSE-295
(which I didn't use
personnally), and from what I've been told this one has also got better.
If someone still thinks the maven-eclipse-plugin has value, then I suggest
that person considers stepping up to maintain that plugin.
2015-12-26 2:12 GMT+01:00 Jeff Jensen :
> >
> > D
>
> Do those of you who are Eclipse users find m2e adequate?
I've successfully used m2e for many years on many different systems
(different customers). I suggest asking about any issues on the m2e users
list.
On Fri, Dec 25, 2015 at 2:37 PM, Gary Gregory
wrote:
> I'm still surprised that no
Op Fri, 25 Dec 2015 21:37:55 +0100 schreef Gary Gregory
:
I'm still surprised that no one wants to maintain this. Do those of you
who
are Eclipse users find m2e adequate? I don't. Unless I do not know how to
set it up. For example, importing the log4j2 projects creates some
projects
with
On Fri, Dec 25, 2015 at 4:22 PM, Gary Gregory wrote:
> Yeah, I've avoid m2e until the other day to see if it got any better. Not.
> So your solution is to switch IDEs... hm, not a huge fan of IJ... is there
> an Eclipse-like Java Perspective? I find file based editing retarded.
I don't understand
Yeah, I've avoid m2e until the other day to see if it got any better. Not.
So your solution is to switch IDEs... hm, not a huge fan of IJ... is there
an Eclipse-like Java Perspective? I find file based editing retarded.
Gary
On Dec 25, 2015 12:49 PM, "Benson Margulies" wrote:
> Eclipse's single
Eclipse's single classpath makes it fundamentally broken with any maven
project that has test dependences. So some of us bailed to intellij long
ago. m-e-p has one set of incurable issues, and m2e, while much improved,
can still eat all your memory on a moderate project.
We've watched the lack of
I'm still surprised that no one wants to maintain this. Do those of you who
are Eclipse users find m2e adequate? I don't. Unless I do not know how to
set it up. For example, importing the log4j2 projects creates some projects
with errors.
Gary
On Dec 24, 2015 2:44 PM, "Michael Osipov" <1983-01...@
Am 2015-12-25 um 14:25 schrieb Robert Scholte:
Op Fri, 25 Dec 2015 13:09:26 +0100 schreef Michael Osipov
[...]
I would continue as instructed by our retirement plan, issue, final
release with notice. Moreover, I would add warning log output to every
mojo that this plugin has been retired.
Sin
Op Fri, 25 Dec 2015 13:09:26 +0100 schreef Michael Osipov
:
Robert,
just read the discussion on mojohaus-dev. Does this actually mean that
you need to respin to vote for complete retirement? I would do so.
I don't see a reason for a respin of the vote: we decided to retire the
plugin an
Robert,
just read the discussion on mojohaus-dev. Does this actually mean that
you need to respin to vote for complete retirement? I would do so.
I would continue as instructed by our retirement plan, issue, final
release with notice. Moreover, I would add warning log output to every
mojo th
Hi Michael,
it was half forgotten, half intended. My original idea was to donate it to
MojoHaus and once they made there first release we could do final release
here and refer to the the maintainers.
However, MojoHaus hasn't found someone to maintain it over there. Other
argument: sources a
Hi Robert,
back in October the result of the retirement vote [1] was positive.
The plugin is still online without notice, issues are still open in JIRA
and no repo is at GitHub.
Did you simply forget that?
Michael
[1] https://www.mail-archive.com/dev%40maven.apache.org/msg107104.html
-
; >> after the migration
> >>
> >> which plugin would (apache, codehaus)
> >>
> >> mvn eclipse:
> >>
> >> picks up?
> >>
> >> Thanks
> >>
> >> -Dan
> >>
> >> On Wed, Oct 7,
te:
>>
>>> Hi,
>>>
>>> as one might already have read: the Apache Maven team has decided to stop
>>> the maintenance of the maven-eclipse-plugin. Even though M2Eclipse does a
>>> great job, some still prefer or need to use the maven-eclipse-
last release... :-/
> >
> > So, +1 on retring and donating it.
> >
> > Btw, are there any changes after the last release that require an
> > additional release now?
> >
> >
> > 2015-10-06 22:54 GMT+02:00 Michael Osipov :
> >
> > >
> mvn eclipse:
>
> picks up?
>
> Thanks
>
> -Dan
>
> On Wed, Oct 7, 2015 at 12:22 PM, Robert Scholte >
> wrote:
>
> Hi,
>
> as one might already have read: the Apache Maven team has decided to stop
> the maintenance of the maven-eclipse
wrong with eclipse:eclipse IMO but I have no spare cycles
>> to maintain it. I'm not sure why Maven wants to go out of its way to break
>> it though...
>> Gary
>>
>> ---- Original message
>> From: Jochen Wiedmann
>> Date: 10/07/20
eak it
> though...
> Gary
>
> Original message
> From: Jochen Wiedmann
> Date: 10/07/2015 23:34 (GMT-08:00)
> To: Maven Developers List
> Subject: Re: [VOTE] Retire Maven Eclipse Plugin / Donation to Mojohaus
>
> On Wed, Oct 7, 2015 at 8:04 PM, Gary G
Maven wants to go out of its way to break it though...
Gary
Original message
From: Jochen Wiedmann
Date: 10/07/2015 23:34 (GMT-08:00)
To: Maven Developers List
Subject: Re: [VOTE] Retire Maven Eclipse Plugin / Donation to Mojohaus
On Wed, Oct 7, 2015 at 8:04 PM, Gary Gr
On Wed, Oct 7, 2015 at 8:04 PM, Gary Gregory wrote:
> Does m2e still want to pollute POMs withcryptic entries?
There are alternative storage possibilities, but that
doesn't fix the inherited difficulties. Just mákes the
SCM purists happy (and forces other users to live with the same
trouble that
> wrote:
>>
>> Hi,
>>>
>>> as one might already have read: the Apache Maven team has decided to stop
>>> the maintenance of the maven-eclipse-plugin. Even though M2Eclipse does a
>>> great job, some still prefer or need to use the maven-eclipse-plugin.
>
:
Hi,
as one might already have read: the Apache Maven team has decided to
stop
the maintenance of the maven-eclipse-plugin. Even though M2Eclipse does
a
great job, some still prefer or need to use the maven-eclipse-plugin.
For this reason the plugin is donated to Mojohaus.
I've done a
of the maven-eclipse-plugin. Even though M2Eclipse does a
> great job, some still prefer or need to use the maven-eclipse-plugin.
> For this reason the plugin is donated to Mojohaus.
>
> I've done a check on the svn history and there is no relevant change after
> the 2.10 release.
&
Hi,
as one might already have read: the Apache Maven team has decided to stop
the maintenance of the maven-eclipse-plugin. Even though M2Eclipse does a
great job, some still prefer or need to use the maven-eclipse-plugin.
For this reason the plugin is donated to Mojohaus.
I've done a
ssues that Karl-Heinz
found during the vote of that last release... :-/
So, +1 on retring and donating it.
Btw, are there any changes after the last release that require an
additional release now?
Based on the svn log all changes after 2.10 had nothing to do with the
maven-eclipse-plu
Am 2015-10-07 um 19:45 schrieb Andreas Gudian:
I was the last one doing a release there, primarily fixing some issues that
blocked it from being much of use for Java 8 projects that share the
.project / .classpath files in SCM.
That is higly discouraged these days. Those should be autogenerated
several issues
with the maven-eclipse-plugin.
It will take quite some time to fix these issues, but is it worth
maintaining it here?
Nowadays the Maven support for Eclipse is good and stable.
The maven-eclipse-plugin has a lot of integration tests which should be
rewritten, because it always
> >> Hi,
> >>
> >> during the latest upgrade of the plugin-parent I faced several issues
> >> with the maven-eclipse-plugin.
> >> It will take quite some time to fix these issues, but is it worth
> >> maintaining it here?
> >> Nowadays t
+1
Op Sun, 04 Oct 2015 11:18:55 +0200 schreef Robert Scholte
:
Hi,
during the latest upgrade of the plugin-parent I faced several issues
with the maven-eclipse-plugin.
It will take quite some time to fix these issues, but is it worth
maintaining it here?
Nowadays the Maven support for
ugin-parent I faced several issues
>> with the maven-eclipse-plugin.
>> It will take quite some time to fix these issues, but is it worth
>> maintaining it here?
>> Nowadays the Maven support for Eclipse is good and stable.
>> The maven-eclipse-plugin has a lot of i
Am 2015-10-04 um 11:18 schrieb Robert Scholte:
Hi,
during the latest upgrade of the plugin-parent I faced several issues
with the maven-eclipse-plugin.
It will take quite some time to fix these issues, but is it worth
maintaining it here?
Nowadays the Maven support for Eclipse is good and
+1
> On Oct 4, 2015, at 5:18 AM, Robert Scholte wrote:
>
> Hi,
>
> during the latest upgrade of the plugin-parent I faced several issues with
> the maven-eclipse-plugin.
> It will take quite some time to fix these issues, but is it worth maintaining
> it here?
>
+1 retire it
4. okt. 2015 11.19 a.m. skrev "Robert Scholte" :
> Hi,
>
> during the latest upgrade of the plugin-parent I faced several issues with
> the maven-eclipse-plugin.
> It will take quite some time to fix these issues, but is it worth
> maintaining it here?
Hi,
+1 from me...moving maven-eclipse-plugin to mojohaus...which makes
contribution simple if someone want to...
Kind regrds
Karl Heinz Marbaise
On 10/4/15 11:18 AM, Robert Scholte wrote:
Hi,
during the latest upgrade of the plugin-parent I faced several issues
with the maven-eclipse
+1
On 4 October 2015 at 20:18, Robert Scholte wrote:
> Hi,
>
> during the latest upgrade of the plugin-parent I faced several issues with
> the maven-eclipse-plugin.
> It will take quite some time to fix these issues, but is it worth
> maintaining it here?
> Nowadays
+1 to retire it at ASF
+1 to fork at MojoHaus to prepare if someone wants to maintain
Regards,
Hervé
Le dimanche 4 octobre 2015 11:18:55 Robert Scholte a écrit :
> Hi,
>
> during the latest upgrade of the plugin-parent I faced several issues with
> the maven-eclipse-plugin.
&g
+1 to retire it
2015-10-04 11:18 GMT+02:00 Robert Scholte :
> Hi,
>
> during the latest upgrade of the plugin-parent I faced several issues with
> the maven-eclipse-plugin.
> It will take quite some time to fix these issues, but is it worth
> maintaining it here?
> Nowadays
want to give him some love.
> >
> > On Sun, Oct 4, 2015 at 11:18 AM, Robert Scholte
> > wrote:
> >
> > > Hi,
> > >
> > > during the latest upgrade of the plugin-parent I faced several issues
> > with
> > > the maven-eclipse-plugin.
>
gt; >
> > during the latest upgrade of the plugin-parent I faced several issues
> with
> > the maven-eclipse-plugin.
> > It will take quite some time to fix these issues, but is it worth
> > maintaining it here?
> > Nowadays the Maven support for Eclipse is good an
+1 to retire it from Apache and to give it to MojoHaus where contributions
are easier if some users want to give him some love.
On Sun, Oct 4, 2015 at 11:18 AM, Robert Scholte
wrote:
> Hi,
>
> during the latest upgrade of the plugin-parent I faced several issues with
> the maven-ec
it is in
Jenkins project as Arno mentioned in ApacheCON.
On Sun, Oct 4, 2015 at 11:18 AM, Robert Scholte
wrote:
> Hi,
>
> during the latest upgrade of the plugin-parent I faced several issues with
> the maven-eclipse-plugin.
> It will take quite some time to fix these iss
On 4 October 2015 at 19:48, Robert Scholte wrote:
> Hi,
>
> during the latest upgrade of the plugin-parent I faced several issues with
> the maven-eclipse-plugin.
> It will take quite some time to fix these issues, but is it worth
> maintaining it here?
> Nowadays the Mave
ing for M2E than using it.
Btw, if it comes to MojoHaus I suppose you plan to change
maven-eclipse-plugin to eclipse-maven-plugin, or do you plan to keep the
GA
as-is for backward compat?
Cheers
2015-10-04 11:18 GMT+02:00 Robert Scholte :
Hi,
during the latest upgrade of the plugin-parent I fa
an to change
maven-eclipse-plugin to eclipse-maven-plugin, or do you plan to keep the GA
as-is for backward compat?
Cheers
2015-10-04 11:18 GMT+02:00 Robert Scholte :
> Hi,
>
> during the latest upgrade of the plugin-parent I faced several issues with
> the maven-eclipse-plugin.
> It
Hi,
during the latest upgrade of the plugin-parent I faced several issues with
the maven-eclipse-plugin.
It will take quite some time to fix these issues, but is it worth
maintaining it here?
Nowadays the Maven support for Eclipse is good and stable.
The maven-eclipse-plugin has a lot of
Hi,
On 5/28/15 3:50 PM, Jeffrey E Care wrote:
Andreas Gudian wrote on 05/27/2015 05:08:33 PM:
The Apache Maven team is pleased to announce the release of the Apache
Maven Eclipse Plugin, version 2.10
This plugin is used to generate Eclipse IDE files (*.classpath,
*.project,
*.wtpmodules
Andreas Gudian wrote on 05/27/2015 05:08:33 PM:
> The Apache Maven team is pleased to announce the release of the Apache
> Maven Eclipse Plugin, version 2.10
>
> This plugin is used to generate Eclipse IDE files (*.classpath,
*.project,
> *.wtpmodules and the .settings folder)
The Apache Maven team is pleased to announce the release of the Apache
Maven Eclipse Plugin, version 2.10
This plugin is used to generate Eclipse IDE files (*.classpath, *.project,
*.wtpmodules and the .settings folder) for use with a project - if the M2E
Eclipse-Plugin does not fit you.
This
ttps://issues.apache.org/jira/issues/?jql=project%20%3D%20MECLIPSE%20AND%20
>> > status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/maven-1187/
>> >
&
D%20
> > status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1187/
> >
> https://repository.apache.org/content/repositories/maven-1187/org/apache/mav
> >
> en
es/maven-1187/
> https://repository.apache.org/content/repositories/maven-1187/org/apache/mav
> en/plugins/maven-eclipse-plugin/2.10/maven-eclipse-plugin-2.10-source-releas
> e.zip
>
> Source release checksum(s):
> maven-eclipse-plugin-2.10-source-release.zip sha1:
>
.apache.org/content/repositories/maven-1187/org/apache/maven/plugins/maven-eclipse-plugin/2.10/maven-eclipse-plugin-2.10-source-release.zip
>
> Source release checksum(s):
> maven-eclipse-plugin-2.10-source-release.zip sha1:
> 691ad83cb0b731c8c0ab5a6c5f105a25cd34f73b
>
> Staging s
Found
/Users/kama/Downloads/maven...
Tests run: 50, Failures: 0, Errors: 5, Skipped: 3
It looks like the contents which is expected seemed to be not part
of the release package...
If i start the tests in the
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plu
s/kama/Downloads/maven...
>> ReadWorkspaceLocationsTest.setUp:57 » FileNotFound
>> /Users/kama/Downloads/maven...
>>
>> Tests run: 50, Failures: 0, Errors: 5, Skipped: 3
>>
>>
>> It looks like the contents which is expected seemed to be not part of the
>
expected seemed to be not part of the
> release package...
>
>
> If i start the tests in the
> https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin
> directory the above tests will run successfully...and don't produce
> errors...
>
>
>
>
&g
: 50, Failures: 0, Errors: 5, Skipped: 3
It looks like the contents which is expected seemed to be not part of
the release package...
If i start the tests in the
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin
directory the above tests will run successfully...and don&#
0%3D%20MECLIPSE%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-1187/
https://repository.apache.org/content/repositories/maven-1187/org/apache/maven/plugins/maven-eclipse-plugin/2.10/maven-eclipse-plugin-2.10-so
ugins/maven-eclipse-plugin/issue-tracking.html
but related to this the majority of the plugins is not uptodate ...
Kind regards
karl Heinz Marbaise
Regards,
Hervé
Le vendredi 1 mai 2015 09:54:47 Martijn Dashorst a écrit :
Would be cool if the site was updated wit the new location of jira
issu
ation of jira
> issues as well.
>
> Martijn
>
> On Thu, Apr 30, 2015 at 10:25 PM, Karl Heinz Marbaise
wrote:
> > Hi,
> >
> > i would like to know if there are any objections to make a final release
> > of
> > the maven-eclipse-plugin ?
> >
&g
Le jeudi 30 avril 2015 19:26:54 Daniel Kulp a écrit :
> > On Apr 30, 2015, at 4:25 PM, Karl Heinz Marbaise
> > wrote:
> >
> > Hi,
> >
> > i would like to know if there are any objections to make a final release
> > of the maven-eclipse-plugin ?
> N
tijn
>
> On Thu, Apr 30, 2015 at 10:25 PM, Karl Heinz Marbaise > wrote:
> > Hi,
> >
> > i would like to know if there are any objections to make a final release
> of
> > the maven-eclipse-plugin ?
> >
> > The reason is simply because it is the las
Would be cool if the site was updated wit the new location of jira
issues as well.
Martijn
On Thu, Apr 30, 2015 at 10:25 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> i would like to know if there are any objections to make a final release of
> the maven-eclipse-plugin ?
>
> Th
> On Apr 30, 2015, at 4:25 PM, Karl Heinz Marbaise wrote:
>
> Hi,
>
> i would like to know if there are any objections to make a final release of
> the maven-eclipse-plugin ?
>
No objections to doing the release. Objection to calling it a final release.
:-)
Dan
&
Hi,
i would like to know if there are any objections to make a final release
of the maven-eclipse-plugin ?
The reason is simply because it is the last plugin on the list which
misses the Maven 2.2.1 minimum
This could make our release map complete here...
as you can see here:
https
Great, Thanks!
I'll do the 2.10 release in a not too distant future.
Am Donnerstag, 9. April 2015 schrieb Joseph Walton :
> I've taken a look at two cleanup tasks for maven-eclipse-plugin.
>
> One is a clearout of long-deprecated classes:
>
> https://issues.apache
I've taken a look at two cleanup tasks for maven-eclipse-plugin.
One is a clearout of long-deprecated classes:
https://issues.apache.org/jira/browse/MECLIPSE-697
and the other is updating the mojos to use annotations:
https://issues.apache.org/jira/browse/MECLIPSE-758
Both
On 18 February 2013 00:50, Gabriele Catania wrote:
> The problem here is that the maven-eclipse-plugin's to-maven mojo, which is
> intended to serve as the default tool to create maven artifact from eclipse
> distributions
Here is where you are reasoning is incorrect.
"to-maven" was always a sto
r case the eclipse devs somehow packaged
their distro incorrectly
Martin-
__
Place long-winded disclaimer here
> Date: Sun, 17 Feb 2013 11:02:30 +0100
> Subject: maven eclipse plugin and source bundles
>
The Eclipse plugin currently has a "workspace" configuration option.
This option directs the plugin to figure out
repo-artifact-to-Eclipse-project dependency substitutions by analyzing
the existing projects in the specified Eclipse workspace.
Rather than have the Eclipse plugin figure
On Tue, Feb 21, 2012 at 11:47 PM, wrote:
>
>
>
> Quoted from:
> http://maven-users.828.n2.nabble.com/Maven-Eclipse-Plugin-doesn-t-include-all-source-paths-in-generated-classpath-file-in-a-Java-Groovy-pt-tp6529511p6532169.html
>
>
> --
>
> Th
On Tue, Feb 14, 2012 at 7:46 PM, Stephen Connolly
wrote:
> And he didn't replace Y.Z either ;-)
I blame sleep deprivation.
Hopefully I didn't stuff up anything else of the process...
-
To unsubscribe, e-mail: dev-unsubscr...@mav
And he didn't replace Y.Z either ;-)
On 14 February 2012 03:02, Barrie Treloar wrote:
> On Tue, Feb 14, 2012 at 12:46 PM, Barrie Treloar wrote:
>> Hi,
>> The vote has passed with the following result :
>>
>> +1 (binding): Barrie Treloar, Benson Margulies, Olivier Lamy, Hervé Boutemy
>> +1 (non b
Hi Barrie!
the version X.Y needed to be replaced as well :P At a first sight, it
looked spam :D
All the best, have a nice day,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Tue, Feb 14, 2012 at 4
On Tue, Feb 14, 2012 at 12:46 PM, Barrie Treloar wrote:
> Hi,
> The vote has passed with the following result :
>
> +1 (binding): Barrie Treloar, Benson Margulies, Olivier Lamy, Hervé Boutemy
> +1 (non binding): Robert Scholte
>
> I will promote the artifacts to the central repo.
Apologies for no
The Maven team is pleased to announce the release of the Maven Eclipse
Plugin, version 2.9
The Maven Eclipse Plugin is used to generate Eclipse IDE files
(*.classpath, *.wtpmodules and the .settings folder) for use with a
project.
http://maven.apache.org/plugins/maven-eclipse-plugin/
[Please
gt; Staging site: (not yet synced)
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.9/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
+1
2012/1/19 Barrie Treloar :
> I'm going to need more +1 to push this through.
> From the other threads it looks like mostly everyone else is using intellij.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For
+1
On Jan 19, 2012, at 3:55 PM, Barrie Treloar wrote:
> I'm going to need more +1 to push this through.
> From the other threads it looks like mostly everyone else is using intellij.
>
> -
> To unsubscribe, e-mail: dev-unsubscr.
I'm going to need more +1 to push this through.
>From the other threads it looks like mostly everyone else is using intellij.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@mav
egration
> I didn't use it now for more than one year thus I cannot tell how it is
> going now but my impediment was to have to choose between
> * m2eclipse which supported a little subset of eclipse features (WTP
> integration didn't work well before JBoss start to investigate on it, ..
te on it, ...),
which was slow/unusable for large projects but which provided for what it
supported a good developer experience.
* maven-eclipse-plugin that had a larger set of feature but that was broken
in many points like the dependency management and its inability to import
parent/aggregators POMs.
2012/1/16 Arnaud Héritier :
> Thanks a lot for this hard wok Barrie
>
> yes it was my problem too Robert.
> ITs are now very difficult to use/maintain and sadly are covering only the
> fact that what we generate is always the same and not that it is working in
> eclipse.
> As far as I remember this
pache.org/**content/repositories/maven-**061/<https://repository.apache.org/content/repositories/maven-061/>
>>
>> Staging site: (not yet synced)
>> http://maven.apache.org/**plugins/maven-eclipse-plugin-**2.9/<http://maven.apache.org/plugins/maven-eclipse-plugin-2.9/>
&g
true&mode=hide&jqlQuery=project+%3D+MECLIPSE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-061/
Staging site: (not yet synced)
http://maven.apache.org/plugins/maven-eclipse-plugin-2.9/
Guide to testing
=project+%3D+MECLIPSE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-061/
Staging site: (not yet synced)
http://maven.apache.org/plugins/maven-eclipse-plugin-2.9/
Guide to testing staged releases:
http://maven.apache.org/guides
On Wed, Dec 21, 2011 at 7:37 PM, zuxiong lin wrote:
> So, your advice is that change the packages layout to use pom dependency
> manager ,
> delete all the packages from WEB-INF/lib directory and add the dependency
> element?
Read the freely available books at http://maven.apache.org/articles.htm
iong lin
> > Date: 2011/12/20
> > Subject: Anyone help me about classpathContainers in
> maven-eclipse-plugin?
> > To: us...@maven.apache.org
> >
> >
> > I have a webapp project under eclipse by my colleage. So it has
> > WEB-INF/lib directory
> > and d
zuxiong lin wrote:
> -- Forwarded message --
> From: zuxiong lin
> Date: 2011/12/20
> Subject: Anyone help me about classpathContainers in maven-eclipse-plugin?
> To: us...@maven.apache.org
>
>
> I have a webapp project under eclipse by my colleage.
-- Forwarded message --
From: zuxiong lin
Date: 2011/12/20
Subject: Anyone help me about classpathContainers in maven-eclipse-plugin?
To: us...@maven.apache.org
I have a webapp project under eclipse by my colleage. So it has WEB-INF/lib
directory
and dependcy packages are put in
Processing classpath for: resource
D:/ide/maven/maven-eclipse-plugin/target/test-classes/projects/project-65-MECLIPSE-642/shared-resources:
output=target/classes, include=[], exclude=[**/*.java], test=false,
filtering=false; default output=target/classes
Thanks Barrie[?]!
On Fri, Oct 14, 2011 at 6:35 AM, Barrie Treloar wrote:
> On Thu, Oct 13, 2011 at 9:21 PM, Yi Xiao
> wrote:
> >
> > Hi devs,
> > I use the maven-eclipse-plugin 2.9-SNAPSHOT to make a maven projec
On Thu, Oct 13, 2011 at 9:21 PM, Yi Xiao wrote:
>
> Hi devs,
> I use the maven-eclipse-plugin 2.9-SNAPSHOT to make a maven project to
Looking into it.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For a
Hi devs,
I use the maven-eclipse-plugin 2.9-SNAPSHOT to make a maven project to
eclipse plugin, I get the error info:
[INFO] Trace
java.lang.StringIndexOutOfBoundsException: String index out of range: -38
at java.lang.String.substring(String.java:1768)
at
m from svn branch. It will
be easier for both sides.
Best regards,
Lukasz
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-eclipse-plugin-tp4634689p4638590.html
Sent from the Maven Developers mailing list archive at
dy ASF commiter and I would like help you with this plugin in part time
> to minimize number of pending issues. For example I've reported an issue in
> 2009 and provided patch. Issue wasn't commented and it wasn't revieved. Any
> ideas how to bring eclipse plugin to life agai
1 - 100 of 876 matches
Mail list logo
