, if there people willing to help (like adding your needed feature
of embedded jars).
regards,
Richard van Nieuwenhoven
Costin Caraivan wrote:
Jason van Zyl-5 wrote:
This is a bad idea and don't count on Maven 3.x supporting this
because it makes determining what the dependencies are black
/display/M2ECLIPSE/Tycho+project+overview
--
Regards,
Igor
Richard van Nieuwenhoven wrote:
Hi,
i am having troubles activating a plexus ArtifactRepositoryLayout
component from a pom. I tried the notation:
extensions
extension
groupIdxxx/groupId
artifactIdxxx/artifactId
versionxxx
way to activate it from inside the pom?
Thanks for any help,
Richard van Nieuwenhoven
My prerequisites (and the solution satisfies them so far):
- use only eclipse plugins that are contained in the same stable version.
- We do not want to pollute the repository with all the versions from
Hi,
i have a strange requirement, i need a possibility to extend the
dependencies of a MavenProject in a plugin or component during build
time. I tried adding dependencies in a validation phase plugin, with no
success.
Is there a official way to do this? Maybe a dynamic profile? Defaults
On Thu, Apr 24, 2008 at 9:33 AM, Richard van Nieuwenhoven [EMAIL PROTECTED]
wrote:
Hi,
i have a strange requirement, i need a possibility to extend the
dependencies of a MavenProject in a plugin or component during build
time. I tried adding dependencies in a validation phase plugin
ideas?
thanks for the help,
Ritchie
Gilles Scokart wrote:
On 24/04/2008, Richard van Nieuwenhoven [EMAIL PROTECTED] wrote:
Hi,
the reason i need it is that a plugin generates code that depends on a
framework in a specific configuration. And the knowledge witch
combination of frameworks
Hi,
the requireMavenVersion also applies to the runtime, but 2.0.8 is just
required for the testing during the build. As far as i know not for the
runtime. We use the plugin in a lot of projects that are locked to maven
2.0.7.
So please limit it only for the build time.
regards,
Ritchie
Hi,
here is my +1
Thanks for the fast release!
Ritchie
Arnaud HERITIER wrote:
Hi,
Since the 2.5 release we did 10 days ago, we solved 3 annoying issues:
* [MECLIPSE-266] - plugin applies java facet to ear project
* [MECLIPSE-411] - manifest property usage is only for ogsi
in maven 2.0.9.
My use case is not really standard, but this may suggest some
regression
either in maven 2.0.9 or the eclipse plugin.
Nicolas
2008/3/28, Richard van Nieuwenhoven [EMAIL PROTECTED]:
Hi,
here is my +1
Thanks for the fast release!
Ritchie
Arnaud
and set it to ${basedir}
Ritchie
Arnaud HERITIER wrote:
Ok. Thx a lot. I'll fix it with the executedProject the next week.
Arnaud
On Fri, Mar 28, 2008 at 12:16 PM, Richard van Nieuwenhoven [EMAIL
PROTECTED] wrote:
hmmm, that seems to be a relict of the old usage of the workspace
variable
Hi,
The problem here is the phase in the life cycle.. The best thing would
be to use the generated application.xml from the ear plugin but thats
generated very late in the packaging phase. The eclipse plugin runs in a
very early phase to be able to generate eclipse config files also for
broken
to
reuse some services throught a shared library
Arnaud
On Thu, Mar 20, 2008 at 9:03 AM, Richard van Nieuwenhoven
[EMAIL PROTECTED] wrote:
Hi,
The problem here is the phase in the life cycle.. The best thing would
be to use the generated application.xml from the ear plugin but thats
Hi,
i did hit the same problem and found that there is a difference in the
version range handling between maven and eclipse plugins.
My solution was rather ugly i used the maven-eclipse-plugin in the
version 2.4 to create a local repository. because that version of the
plugin ignores the version
+1
Ritchie
Arnaud HERITIER wrote:
Hi,
We solved more than 50 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593styleName=HtmlprojectId=11133
Important changes are :
- Add support for WTP 2.0
- Add support for MyEclipse
- Improve RAD6 support
- Posibility to discover
Hi,
The original use of this parameter was for this strange effect. When i
introduced the new parameter i called it workspaceToConnect because the
parameter workspace was in use.
Arnaud fixed a jira (don't remember the number) that this effect has
nothing to do with the workspace and renamed it,
ok, just changed my mind. after reading all comments and looking into my
needs now. I can work with with the mapping, specially because i need
only one at the moment.
It is MUCH more important there is a consistent mapping! Than it is that
somebody like me likes it or not.
Just see a lot of work
and plugin.
Ritchie
Carlos Sanchez wrote:
why would we use groupIds and artifactIds if we were going to repeat
the same information in both fields?
this was already brought before and the way the jars are stored
doesn't imply the way they are used
On Nov 27, 2007 8:12 PM, Richard van
it is.
Ritchie
Carlos Sanchez wrote:
On Nov 28, 2007 6:40 PM, Richard van Nieuwenhoven [EMAIL PROTECTED] wrote:
The reason for me is that eclipse is the source of the jars and eclipse
does repeat the group name in the jar name.
It looks very strange to have 10 different jars in the classpath all
be used as id
You have to consider that the repository is not only for Maven users
On Nov 28, 2007 7:51 PM, Max Bowsher [EMAIL PROTECTED] wrote:
Carlos Sanchez wrote:
On Nov 28, 2007 6:40 PM, Richard van Nieuwenhoven [EMAIL PROTECTED] wrote:
The reason for me is that eclipse is the source
I think it is important that {artifactId}-{version}.jar results in a
name as similar as possible the the name as they are in the plugin
directory of eclipse.
And the eclipse project name should represent the group id of the plugin
as on http://www.eclipse.org/projects/ , whereas i do not care if
(IBM - EPL 1.0). Those sources are in
src/main/eclipse
with the license file.
Can I add them, or is it prohibited ?
Arnaud
On Nov 14, 2007 4:37 AM, Brett Porter [EMAIL PROTECTED] wrote:
On 13/11/2007, at 4:37 AM, Richard van Nieuwenhoven wrote:
I see different solutions, but witch
/eclipse/org/eclipse/core/org.eclipse.core.resources/3.2.1/
Arnaud
On Nov 26, 2007 1:57 PM, Richard van Nieuwenhoven [EMAIL PROTECTED] wrote:
just that it is not the maven2 central repository.
It is the maven1 repository or is that wrong / or a problem?
Ritchie
Arnaud HERITIER wrote:
Ok
/org.eclipse.core.resources/3.2.1/
Arnaud
On Nov 26, 2007 1:57 PM, Richard van Nieuwenhoven [EMAIL PROTECTED]
wrote:
just that it is not the maven2 central repository.
It is the maven1 repository or is that wrong / or a problem?
Ritchie
Arnaud HERITIER wrote:
Ok, it's cool.
Thus we just have to add
All,
with a very small code change and 2 small sources from a eclipse-plugin
the maven-eclipse-plugin will be able to connect projects to the
projects in the workspace instead of the jars for the repository. This
is a very important feature for the maven-eclipse-plugin.
Now to my question:
To do
(this will reduce a lot of rad problems)
regards,
Richard van Nieuwenhoven
Hemant Ved wrote:
Hi all
Can anybody explain me the steps to deploy ejb using maven with Websphere
6?Has anybody tried using Maven and RAD combination? Can maven follow the
directory structure of RAD?
Thanks and regards
modules from
this project as separate eclipse-projects
This works very good, just like using symbolic links in Unix.
Richard van Nieuwenhoven
Syte Beimin wrote:
First of all I hope this is the right place to send my patch to.
At my company we're used to check out an entire project from
subversion
Hello,
my patch http://jira.codehaus.org/browse/MECLIPSE-213 contains a fix for
this problem.
i have also a better version that takes it from the ear-plugin
configuration because there
there is a property *defaultLibBundleDir
test are missing correct, but a fix for this ear problem is rather
important because
ear's won't work with WTP as they are.
Ritchie
Brian E. Fox wrote:
Same thing with this one, the patch doesn't exist yet along with tests
or doc changes. If we have to respin the release because of the test
the
patch. It's a recurring cycle where we wait and wait and before you know
it, it's 5 months like it is now with good functionality already sitting
there.
--Brian
-Original Message-
From: Richard van Nieuwenhoven [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 05, 2007 9:21 AM
Hello,
i developed a rad-6 maven plugin based on the eclipse plugin for a big
customer who want's to use maven-2.
It was developed because i could not find a rad-6.0 capable maven plugin
that realy works.
My customer allowed me to release the code, now my question is how to do it
- where
:
What does it do above and beyond the normal eclipse plugin? I ask
because we are using RAD here and it works fine with the normal plugin.
-Original Message-
From: Richard van Nieuwenhoven [mailto:[EMAIL PROTECTED]
Sent: Friday, July 28, 2006 8:13 AM
To: Maven Developers List
Subject
31 matches
Mail list logo
