You can just run a goal to generate the .classpath and add the maven repo...
http://maven.apache.org/reference/plugins/eclipse/goals.html
-Original Message-
From: Kenneth Simpson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 27, 2004 2:24 AM
To: [EMAIL PROTECTED]
Subject: Re:
it helps in some cases, but I still want to change xml parser for maven. I want to use
JVM's default parser. why maven specifies XML Parser? I think this is bad. users must
be able to choose their own parser without modifying maven script and classpath.
- Original Message -
From: John
Requirement: for a large internal artefact repository
for Maven, I would like to be able to password protect
certain directories, using HTTP basic authentication.
The contents are sensitive, and the internal network
is large.
It seems like Maven does not support this directly,
and that the
The issue isn't the number of source directories, it's the location.
product-ejb has in the project.xml sourceDir../product/source/src/sourceDir
This isn't allowed in eclipse.
I could set it to an absolute path, but that's nasty as it assumes
everyone checks out in the same location.
On Tue,
The reason is simple - the crimson parser bundled with the JDK's through
1.4.2(?) is complete crap. Additionally, even older JDK's don't have a
parser bundled, which means you'd have to create multiple maven distros
(one for parser-bundled JDKs and another which accounted for the xml
parser).
On Wed, 2004-10-27 at 10:00, Haile, Mussie wrote:
I am running into the same problem you are and I don't think Maven supports
Password protection for its Repository; they only way I can think of do this
would be to setup Proxy server.
Basic auth is supposed to work in the form:
Is anyone using Maven to build Eclipse plugins and package
them as an RCP application?
We are starting a new project - this seems to be a good opportunity
to give Maven a try. The project will consist of building many
plugins and bundling them into an installable package. The similarity
of the
I know the guys @ http://mevenide.codehaus.org have a maven plugin to
help build eclipse plugins.
Don't know about the RCP stuff tho.
On Wed, 27 Oct 2004 10:54:53 -0400, Christopher L Merrill
[EMAIL PROTECTED] wrote:
Is anyone using Maven to build Eclipse plugins and package
them as an RCP
I'm having a similar problem. Here's the relevent parts of my POM:
dependencies
dependency
groupIdmaven/groupId
artifactIdmaven-jxr-plugin/artifactId
version1.4.2/version
typeplugin/type
/dependency
/dependencies
reports
reportmaven-jxr-plugin/report
The reason is simple - the crimson parser bundled with the JDK's through
1.4.2(?) is complete crap. Additionally, even older JDK's don't have a
parser bundled, which means you'd have to create multiple maven distros
(one for parser-bundled JDKs and another which accounted for the xml
I'm interested in why you need MS949 for project.xml. The reason I ask
is that we intend to switch to a smaller, faster XML parser in Maven
1.1, however it is likely to support fewer encodings and xml features
- but still supports everything required to correctly operate Maven
that we have found
I'm interested in why you need MS949 for project.xml. The reason I ask
is that we intend to switch to a smaller, faster XML parser in Maven
1.1, however it is likely to support fewer encodings and xml features
- but still supports everything required to correctly operate Maven
that we have
TWIMC,
Here's my first maven plugin. :)
Any comments are welcome. (Especially in the documentation. I'm so bad
at writing documentation.)
The Maven-DocCheck team is pleased to announce the Maven DocCheck Plugin
1.4-0.1 release!
http://maven-doccheck.sourceforge.net/
Changes in this
13 matches
Mail list logo
