Hello,
I've found that some providers have implementation for INFO command, for
example SvnExeScmProvider and GitExeScmProvider (partially),
but the problem is in that ScmProvider interface does not support info
command, so how the implementation can be used now?
--
Best regards,
Sergey
Hi,
I intend to move the ganymed SSH provider to the sandbox. That library
is no longer supported (though it has seen recent development at a new
home that might be promising - they are even looking at an SSH server
that'd be good for testing). Given that the JSCH version has been
stable
In light of this, I think the best thing to do is:
- rename to webdav-jackrabbit
- have no -webdav module in the final release
- make sure wagon-webdav 1.0-beta-2 works with the new API
Cheers,
Brett
On 22/05/2008, at 1:01 AM, Jason van Zyl wrote:
On 20-May-08, at 9:17 AM, Brian E. Fox
Hi,
the staging is not working : Page Not Found !
Frederic DROUET
On Thu, May 22, 2008 at 5:53 AM, Vincent Siveton [EMAIL PROTECTED]
wrote:
Hi,
According the Doxia release process [1], I would like to release Maven
Doxia Tools 1.0.
There are still a couple of issues left in JIRA:
Hi,
I am a newbie in Junit Report. Can you give me procedures or steps on how
to setup Junit report in eclipse. I would appreciate any help from you.
Thanks
Robert
DISCLAIMER: The information in this electronic message is privileged and
confidential, and is intended only for use of the
+1
--
Olivier
2008/5/21 Daniel Kulp [EMAIL PROTECTED]:
The PMD plugin has had a bunch of bugs fixed and and other improvements that
should be pushed out to the users:
** Bug
* [MPMD-61] - When running build using -f path_to_pom/pom.xml the site
is stored in working directory instead of
+1
--
Olivier
2008/5/20 Vincent Siveton [EMAIL PROTECTED]:
Hi,
We solved 13 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11124styleName=Htmlversion=13504
There are still a 0 of issues left in JIRA, yes 0, thanks Benjamin! :) :
Yep, my ongoing saga with conflict resolution is detailed here:
http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers
http://jira.codehaus.org/browse/MNG-612
Would be great to get this resolved.
Mark
2008/5/22 Brett Porter [EMAIL PROTECTED]:
That's what I was referring to.
On
+1
Thanks,
--
Olivier
2008/5/21 Mark Hobson [EMAIL PROTECTED]:
Hi there,
I'd like to attempt to release Maven Runtime 1.0-alpha-1 again. The
changes since the last vote are:
- Upgraded to Java 5
- Sped up tests
- Added site documentation and reports
- Tidied code and Javadoc
Staging
Hi,
2008/5/22, Frederic DROUET [EMAIL PROTECTED]:
Hi,
the staging is not working : Page Not Found !
It is due to the sync.
Work this morning.
Cheers,
Vincent
Frederic DROUET
On Thu, May 22, 2008 at 5:53 AM, Vincent Siveton [EMAIL PROTECTED]
wrote:
Hi,
According the Doxia
It looks like Jason's original message was tossed by out mail server
as junk. I'm not sure why. Anyway, we use HTTP (hosted by
Artifactory), but I would not be infavor of eliminating the
possibility of other protocols.
-Josh
On May 22, 2008, at 1:03 AM, Brett Porter wrote:
2008/5/21
Improved dependency version conflict resolution, and a lot of other important
issues either require or would benefit from changing the pom model. As far as I
can tell, there have not yet been any changes to this model in the 2.1 branch.
So I was wondering what should be the strategy for
On 22-May-08, at 7:28 AM, Paul Gier wrote:
Improved dependency version conflict resolution, and a lot of other
important issues either require or would benefit from changing the
pom model. As far as I can tell, there have not yet been any
changes to this model in the 2.1 branch. So I was
I do agree with artifactId == bundle symbolic name (you meant bundle
symbolic name, not bundle id, right?) but I think there is more to it.
Consider the following four usecase
* Create new Maven artifact from existing eclipse/osgi bundle. This
happens when eclipse bundles are deployed into a
Here's my 2c.
- Bundle-SymbolicName = artifactId is a no-brainer IMHO
- groupId should be the organization creating the bundle (so when
converting an existing library, the organization that does the
converting)
- Bundle-Version = version - somebody once proposed dropping the
qualifier but then
On 22-May-08, at 8:10 AM, Tom Huybrechts wrote:
Here's my 2c.
- Bundle-SymbolicName = artifactId is a no-brainer IMHO
- groupId should be the organization creating the bundle (so when
converting an existing library, the organization that does the
converting)
- Bundle-Version = version -
So can we make changes to the model in 2.1, or do we have to work
with the existing model?
Provide we retain the behavior of old with a flag if the user desires
with 2.1 the door is wide open to correct anything we see fit.
It's more than that, the poms deployed to central should conform
Done
Jason Dillon wrote:
Thanks, you should update its category so it shows up in the Maven
Technologies group list.
--jason
On May 21, 2008, at 10:09 PM, Brett Porter wrote:
MARTIFACT
On 22/05/2008, at 1:07 AM, Jason Dillon wrote:
I've got a patch waiting which adds type information
Mark, can we please have a big sign somewhere prominently on the site
informing users that Maven Runtime requires Java 5. I was not able to
find info on this on the staged site.
I think people have gotten used to Maven stuff requiring only Java 1.4.
So any product that we release that
Vincent, this commit has changed the case for the characters inside
unicode strings, from upper care to lower case. Was that intentional?
I don't know if case matters for such strings.
An example:
-report.cim.overview.title = \u00DCbersicht
+report.cim.overview.title = \u00dcbersicht
[EMAIL
Hi Dennis,
2008/5/22, Dennis Lundberg [EMAIL PROTECTED]:
Vincent, this commit has changed the case for the characters inside unicode
strings, from upper care to lower case. Was that intentional?
Nope. It is the Eclipse Plugin
I don't know if case matters for such strings.
An example:
On May 21, 2008, at 9:56 AM, Jason van Zyl wrote:
Bryon,
How would you compare this with a method like this using XML Schema.
I'm not a huge fan of XSD, but there is a lot of tooling for XSD
especially in IDEs and that would be something we have to consider.
Do you actually use this
In particular, could you compare in detail this relaxng method and
the similar xml schema approach using substitution groups and
abstract schema types? (note that the substitution group part of
this is unnecessary but results in easier to read xml)? After
studying your blog post I
Are there any tools like jaxb that work with relaxng?
To the best of my knowledge, there are not (for java). The language
binding frameworks for RelaxNG that I have seen generally involve
annotating the RelaxNG grammar with explicit hints about how to map
schema elements to object model
Issue Subscription
Filter: Design Best Practices (29 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-3313NetBeans projects, more than ant project, more than
25 matches
Mail list logo
