Jochen Wiedmann wrote:
On 7/3/07, Mark Hobson [EMAIL PROTECTED] wrote:
Following the recent thread Maven POM plugin config, this is a vote
to add downloadSources=true to both the eclipse and idea plugin
configurations in the maven-parent POM:
[ ] +1: I like Javadoc and easy debugging
[ ] +0:
Jason van Zyl wrote:
Hi,
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/
Here is the JIRA roadmap:
Graham Leggett wrote:
Hi all,
It seems that http://jira.codehaus.org/browse/CONTINUUM-734 Can't use
continuum behind https proxy still hasn't been resolved, which is a
serious oversight.
Looking at the code, is this a continuum problem or a plexus problem?
Has there been any progress on
According to the two mails below from [EMAIL PROTECTED], starting with today a PMC
isn't allowed to release an artifact if the sources don't cover the new
copyright header policy (second mail). Additionally we need to add LICENSE and
NOTICE files inside jars too (first mail).
Has the
Rinku wrote:
Hi,
Not sure if there is some work in progress for Eclipse Plugin support
but here are some quick notes on the following logged in JIRA
http://jira.codehaus.org/browse/MECLIPSE-92
http://jira.codehaus.org/browse/MECLIPSE-103
1) Running eclipse:eclipse should generate the project
Rinku wrote:
snip/
So far I added the configuration parameter pde. If set to true, the
PluginNature and the schema and manifest builders are added to .project.
I have a patch submitted for this for the maven-eclipse-plugin. Though
not sure when that gets integrated into the plugin. IMHO
Geoffrey De Smet wrote:
I created a mvnd script and there is an issue for it.
After that it's just a matter of creating a remote debugger in eclipse.
Would you mind sharing the issue link with us?
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering,
[ http://jira.codehaus.org/browse/MECLIPSE-71?page=comments#action_60229 ]
Reinhard Poetz commented on MECLIPSE-71:
Are there any implications if I don't run eclipse:clean before I run
eclipse:eclipse? Is it possible that the plugin creates some
[ http://jira.codehaus.org/browse/MECLIPSE-71?page=comments#action_59893 ]
Reinhard Poetz commented on MECLIPSE-71:
ok, this makes it even easier :-)
AFAICS, the SettingsWriter writes to org.eclipse.jdt.core.prefs. It doesn't
generate the complete
[ http://jira.codehaus.org/browse/MECLIPSE-70?page=all ]
Reinhard Poetz updated MECLIPSE-70:
---
Attachment: patch_removeDuplicateEntries.diff
Duplicate entries in .project (/projectDescription/projects/project
, Reinhard Poetz wrote:
We'll have to look into that, but you're using a very old eclipse
plugin, since the downloadSources is false by default.
-- Kenney
John Casey wrote:
snip/
If you're interested, you can take the current release candidate for a
test drive. The RC tarball is at:
http
I have a pom.xml, which declares following dependencies:
dependency
groupIdcom.mycompany/groupId
artifactIdapp-framework/artifactId
version1.0-SNAPSHOT/version
typejar/type
/dependency
dependency
groupIdcom.mycompany/groupId
artifactIdapp-framework/artifactId
eclipse:clean delets too much
-
Key: MECLIPSE-71
URL: http://jira.codehaus.org/browse/MECLIPSE-71
Project: Maven 2.x Eclipse Plugin
Type: Bug
Versions: 2.1
Reporter: Reinhard Poetz
If I call eclipse:clean, the complete
[ http://jira.codehaus.org/browse/MECLIPSE-71?page=comments#action_59810 ]
Reinhard Poetz commented on MECLIPSE-71:
My idea was adding a configuration parameter, that makes it possible to add
paths that are excluded from deletion.
WDYT
If I call eclipse:clean, the complete .settings directory is deleted. In some
of my projects we share some Eclipse settings in our team by adding the
.settings directory to SVN.
The behaviour of deleting the comlete .settings directory is unpractical for us
as SVN gets confused by the missing
, 2.0, 2.1
Reporter: Reinhard Poetz
If a pom.xml has following dependencies
dependency
groupIdcom.mycompany/groupId
artifactIdapp-framework/artifactId
version1.0-SNAPSHOT/version
typejar/type
/dependency
dependency
groupIdcom.mycompany
[ http://jira.codehaus.org/browse/MECLIPSE-70?page=all ]
Reinhard Poetz updated MECLIPSE-70:
---
Attachment: patch_removeDuplicateEntries.diff
Duplicate entries in .project (/projectDescription/projects/project
John Casey wrote:
snip/
If you're interested, you can take the current release candidate for a
test drive. The RC tarball is at:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060222.031501.tar.gz
As I had some problems with Maven 2.0.2 I tried to use this RC.
18 matches
Mail list logo