On 5/17/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Mike Perham wrote on Tuesday, May 16, 2006 9:31 PM:
> Any ETA? I haven't seen any status emails like I did with the Apache
> problems.
Well, Ben gave an ETA indicating the outage would take half an hour, but this
was already some days ago.
yup the test case also indicates that behavior, it is great the have test
around so that
one can figure out what the feature means.
However, I am still having trouble why filtered is set to true, the orignal
source file is transformed into
fullpath before added to the archiver.
Also where in th
Mike Perham wrote on Tuesday, May 16, 2006 9:31 PM:
> Any ETA? I haven't seen any status emails like I did with the Apache
> problems.
Well, Ben gave an ETA indicating the outage would take half an hour, but this
was already some days ago. Since the mailing lists (even the Codehaus internal)
when filtered is true, it means expressions like
${project.build.directory} inside the file is replaced with the actual
value when used in your pom.xml
dan tran wrote:
Hello, I am trying to fix
http://jira.codehaus.org/browse/MASSEMBLY-100 and
having trouble
understanding the purpose of ele
Hi Dan,
It is like the of resources where the expression in resource
files such as LICENSE.txt can be interpolated.
Hope this helps,
allan
dan tran wrote:
Hello, I am trying to fix
http://jira.codehaus.org/browse/MASSEMBLY-100 and
having trouble
understanding the purpose of element in F
hmmm... you're right.
Seems like assembly is excluding all META-INF/plexus/components.xml and
creating/adding the temp file for it even if the file is NOT in include
and/or is excluded. This IS a bug.
I'll create a jira issue for this
Brett Porter wrote:
META-INT?
[EMAIL PROTECTED] wrot
Hello, I am trying to fix http://jira.codehaus.org/browse/MASSEMBLY-100 and
having trouble
understanding the purpose of element in FileItem if the
descriptor.
Could someone or the owner of that feature explains what it really means?
Thanks
-Dan
On 5/17/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
tmatesoft JavaSVN is the problem, not SVN per se
http://tmate.org/svn/licensing/index.html
Ah, thought the previous post was referring to JavaSVN.
Maybe still worth talking to them.
Please join legal discussion if you want to discuss the l
tmatesoft JavaSVN is the problem, not SVN per se
http://tmate.org/svn/licensing/index.html
Please join legal discussion if you want to discuss the legal terms,
but as I understand it's pretty clear. It's similar case as GPL, where
apache software can't depend on it, no matter if we just use it.
Either way if they give you guys trouble you can try sending chuck norris in
;) (sorry, just loved that signature..heh)
On 5/16/06, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> Where is the license problem? With JavaSVN or SVN? According to
> tigris.org, svn is using an apache compatible license.
Where is the license problem? With JavaSVN or SVN? According to
tigris.org, svn is using an apache compatible license.
Maybe they are not aware that it is not?
Maybe this can be resolved by talking to them ...so they might fix that.
cheers
--
Torsten
---
Where is the license problem? With JavaSVN or SVN? According to
tigris.org, svn is using an apache compatible license.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Tuesday, May 16, 2006 2:47 PM
To: Maven Developers List
Subject: Fw
Is that really the only problem with the license? Since noone would be
making changes to the source, does that condition apply at all?
On 5/17/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
FYI seems that we won't be able of having a java implementation of
svn. In fact I think we have to remove
FYI seems that we won't be able of having a java implementation of
svn. In fact I think we have to remove it from apache
-- Forwarded message --
From: Justin Erenkrantz <[EMAIL PROTECTED]>
Date: May 16, 2006 12:28 PM
Subject: Re: javasvn license
To: Mario Ivankovits <[EMAIL PROTEC
Rinku wrote:
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 you w
Any ETA? I haven't seen any status emails like I did with the Apache
problems.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Brett,
My apologies, I must look first indeed and tell you about the real
problem, instead of start geussing.
It's just I had it today and yesterday on my work computer,
saw users complaining on the user list and also got a mail from a couple
people from spring-richclient.
I cannot reproduce
Hi Reinhard,
Some notes inlined..
1) Running eclipse:eclipse should generate the project definition
just as it does now, it detects if a "org.eclipse.pde.PluginNature"
is specified for .project and setups the PDE nature (updates to
.classpath) accordingly.
2) A Bundle Manifest writer could
yes, it is:
http://repo.mergere.com/maven2/org/apache/maven/doxia/doxia/1.0-alpha-8/
Please:
a) look first
b) look at the messages on the users list that indicate what the real
problem was.
- Brett
Geoffrey De Smet wrote:
Just noticed (before your answer) I talked about the wrong pom:
It's d
Just noticed (before your answer) I talked about the wrong pom:
It's doxia-1.0-alpha-8 that isn't there.
Downloading:
http://snapshots.maven.codehaus.org/maven2/org/apache/maven/doxia/doxia/1.0-
alpha-8/doxia-1.0-alpha-8.pom
[INFO]
--
yes, it is:
http://repo.mergere.com/maven2/org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-8/
Geoffrey De Smet wrote:
Just to double check if you guys are aware of this problem?
mvn -U site = build-fails because doxia-renderer alpha 8 not on mergere
repo (=stopgap for repo1.maven.org bein
Just to double check if you guys are aware of this problem?
mvn -U site = build-fails because doxia-renderer alpha 8 not on mergere
repo (=stopgap for repo1.maven.org being out due to codehaus.org disk
failure).
If plugin versions are locked down this means every build fails.
It was mentioned
META-INT?
[EMAIL PROTECTED] wrote:
Author: epunzalan
Date: Tue May 16 00:38:59 2006
New Revision: 406865
URL: http://svn.apache.org/viewcvs?rev=406865&view=rev
Log:
MASSEMBLY-88
found the most probably cause for the continuum build failure... the
capitalization of fileset
Modified:
mave
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
Thanks a lot Emmanuel
Emmanuel Venisse a écrit :
http://jira.codehaus.org/browse/MPA-72
Emmanuel
Nicolas De Loof a écrit :
I can't select "Maven Project Administration" in Jira "create bug"
page :
http://jira.codehaus.org/secure/CreateIssue!default.jspa
BUT I can search for issues on thi
http://jira.codehaus.org/browse/MPA-72
Emmanuel
Nicolas De Loof a écrit :
I can't select "Maven Project Administration" in Jira "create bug" page :
http://jira.codehaus.org/secure/CreateIssue!default.jspa
BUT I can search for issues on this project... Is this a JIRA
configuration bug ? Would
26 matches
Mail list logo
