of Nexus yet.
I've just installed it and I'm currently trying it on my local machine.
I have not idea if Nexus can handle documentation releases.
I'm going to test that.
Pierre-Arnaud
On 3/12/10 1:32 PM, Pierre-Arnaud Marcelot wrote:
Hi Stefan and Emmanuel,
As you've started to +1 the idea, maybe it would be better to start a real
formal vote.
So here it is.
[X] +1 - Let's switch to Apache's Nexus repository infrastructure for the next
releases of the Directory project
automatically via scp by maven,
was I wrong ?
I'm not really a pro of Nexus yet.
I've just installed it and I'm currently trying it on my local machine.
I have not idea if Nexus can handle documentation releases.
I'm going to test that.
It looks like the Nexus Professional does have
On 12 mars 2010, at 13:56, Felix Knecht wrote:
It looks like the Nexus Professional does have such a feature, but I
don't now which Nexus is used and if (whenever) it's enabled and used.
See 'Hosting Project Web Sites' [1]
Interesting...
Version used at the ASF is: Sonatype Nexus™
[ X ] +1 - Let's switch to Apache's Nexus repository infrastructure for the
next releases of the Directory project
have seen it at work last year, think we should give it a try
Kiran Ayyagari
On Fri, Mar 12, 2010 at 2:32 PM, Pierre-Arnaud Marcelot p...@marcelot.net
wrote:
[ ] +1 - Let's switch to Apache's Nexus repository infrastructure for the
next releases of the Directory project
[ X ] ±0 - Abstain
[ ] -1 - Let's keep our current deployment mechanism on people.apache.org
Hi everyone,
I'd like to propose that we use Apache's Nexus repository infrastructure to
release our future versions on Maven repositories.
It's used by a large number of Maven based Apache projects now, and it's the
recommended way of uploading releases to Maven Repositories, as described
,
I'd like to propose that we use Apache's Nexus repository infrastructure to
release our future versions on Maven repositories.
It's used by a large number of Maven based Apache projects now, and it's the
recommended way of uploading releases to Maven Repositories, as described on
the Releasing
.
It's used by a large number of Maven based Apache projects now, and it's the
recommended way of uploading releases to Maven Repositories, as described on
the Releasing A Maven Project Guide [1].
I think we've reach the limit with deployments on people.apache.org... My
last deployment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
The guide has a red box on top indicating we're using maven 2.0.6 and about
some problems about deploying (I suppose
this is when releasing) using other than JDK1.5.
- - Is anybody still using maven 2.0.6 or can we update this to 2.0.9?
- -
Hi Felix,
On Wed, Sep 17, 2008 at 10:31 AM, Felix Knecht [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
The guide has a red box on top indicating we're using maven 2.0.6 and about
some problems about deploying (I suppose
this is when releasing) using other
Felix Knecht wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
The guide has a red box on top indicating we're using maven 2.0.6 and about
some problems about deploying (I suppose
this is when releasing) using other than JDK1.5.
It has to be changed.
- - Is anybody still using
Same sentiments ...
Alex
On Tue, Sep 2, 2008 at 9:30 AM, Emmanuel Lecharny [EMAIL PROTECTED]wrote:
Pierre-Arnaud Marcelot wrote:
Hi all,
I know that a 1.5.4 version of Apache DS is currently in preparation and
could be ready very soon. I think it's a matter of days now, right ?
Yep. We
generation and -Prelease
Use the rat maven plugin with the -Prelease profile option to generate
releases
---
Key: DIRSTUDIO-272
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-272
Hi all,
I know that a 1.5.4 version of Apache DS is currently in preparation and
could be ready very soon. I think it's a matter of days now, right ?
Stefan and I were thinking about releasing a new version of Apache Directory
Studio very soon too, 1.3.0 (RC1 first, and final later).
Even if
Pierre-Arnaud Marcelot wrote:
Hi all,
I know that a 1.5.4 version of Apache DS is currently in preparation and
could be ready very soon. I think it's a matter of days now, right ?
Yep. We still have around 10 issues opened, and I'm just reviewing them atm.
Stefan and I were thinking about
/reporting
If ever IMO the rat:check should be added to the
directory/project/trunk/pom.xml release-profile to be used all over the place
for directory subprojects
WDOT?
Use the rat maven plugin with the -Prelease profile option to generate
releases
idea!
+1
Use the rat maven plugin with the -Prelease profile option to generate
releases
---
Key: DIRSTUDIO-272
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-272
, the second or both?
Use the rat maven plugin with the -Prelease profile option to generate
releases
---
Key: DIRSTUDIO-272
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-272
Heads UP!
Before adding patch, are all aware of the impacts It'll be hard to
release anything!
project/trunk: Too many unapproved licenses: 15
apacheds/trunk: Too many unapproved licenses: 1625
shared/trunk: Too many unapproved licenses: 942
studio/trunk: Too many unapproved licenses: 2323
profile
Use the rat maven plugin with the -Prelease profile option to generate
releases
---
Key: DIRSTUDIO-272
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-272
Project
.
But, is this going to forbid us to release a version?
Use the rat maven plugin with the -Prelease profile option to generate
releases
---
Key: DIRSTUDIO-272
URL: https
the rat maven plugin with the -Prelease profile option to generate
releases
---
Key: DIRSERVER-1125
URL: https://issues.apache.org/jira/browse/DIRSERVER-1125
Project
option to generate
releases
---
Key: DIRSERVER-1125
URL: https://issues.apache.org/jira/browse/DIRSERVER-1125
Project: Directory ApacheDS
Issue Type: Improvement
with the -Prelease profile option to generate
releases
---
Key: DIRSERVER-1125
URL: https://issues.apache.org/jira/browse/DIRSERVER-1125
Project: Directory ApacheDS
Issue Type
[
https://issues.apache.org/jira/browse/DIR-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny reassigned DIR-229:
-
Assignee: Emmanuel Lecharny (was: Alex Karasulu)
Old releases should be deleted from dist
have to be cleaned.
Old releases should be deleted from dist directory structure
Key: DIR-229
URL: https://issues.apache.org/jira/browse/DIR-229
Project: Directory
Issue Type: Bug
is in
www/www.apache.org/dist/directory
Old releases should be deleted from dist directory structure
Key: DIR-229
URL: https://issues.apache.org/jira/browse/DIR-229
Project: Directory
Old releases should be deleted from dist directory structure
Key: DIR-229
URL: https://issues.apache.org/jira/browse/DIR-229
Project: Directory
Issue Type: Bug
**The Eclipse Foundation today announced the availability of Eclipse
Higgins 1.0, a freely downloadable identity framework designed to integrate
identity, profile and social relationship information across multiple sites,
applications and devices using an extensible set of components.
with the -Prelease profile option to generate
releases
---
Key: DIRSTUDIO-272
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-272
Project: Directory Studio
Issue
Hi all,
Some folks ask for a refresher on how we deploy our project artifacts.
Here's where you can find the doco on this process:
http://cwiki.apache.org/DIRxDEV/guide-to-directory-releases.html
HTH,
Alex
Use the rat maven plugin with the -Prelease profile option to generate releases
---
Key: DIRSERVER-1125
URL: https://issues.apache.org/jira/browse/DIRSERVER-1125
Project
Use the rat maven plugin with the -Prelease profile option to generate releases
---
Key: DIRSTUDIO-272
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-272
Project
is in protecting our promise to users. 1.0.1,
1.0.2 ... 1.0.x are stablizing and (should) only be bug fix releases
with no API changes. 1.5.1, 1.5.2 ... 1.5.X are potentially
destabilizing and may break with the API and formats for storage etc.
Our promise to users is simple. You should
=542668
Log:
Removed old site scripts.
Removed:
directory/project/releases/7/resources/generate_modules_index_xdoc.sh
directory/project/releases/7/resources/pomartifactId.sh
directory/project/releases/7/resources/pomdesc.sh
directory/project/releases/7/resources
$ svn propget svn:externals
apacheds https://svn.apache.org/repos/asf/directory/apacheds/trunk
shared https://svn.apache.org/repos/asf/directory/shared/trunk
daemon https://svn.apache.org/repos/asf/directory/daemon/trunk
project http://svn.apache.org/repos/asf/directory/project/releases/7
On 5
apacheds
https://svn.apache.org/repos/asf/directory/apacheds/trunk
shared
https://svn.apache.org/repos/asf/directory/shared/trunk
daemon
https://svn.apache.org/repos/asf/directory/daemon/trunk
project
http://svn.apache.org/repos/asf/directory/project/releases/7
On 5/30/07, Alex Karasulu
Oh so it is https in your entries file? This is very odd.
I really want to figure out what's up here because as a general tactic I
like to protect
externals to releases with URL's using the HTTP schema which I always
thought did
not allow commits at the ASF repo.
Alex
On 5/30/07, Ersin Er
:
directory/project/releases/7/resources/generate_modules_index_xdoc.sh
directory/project/releases/7/resources/pomartifactId.sh
directory/project/releases/7/resources/pomdesc.sh
directory/project/releases/7/resources/pomdistSiteUrl.sh
directory/project/releases/7/resources
: 542668
URL: http://svn.apache.org/viewvc?view=revrev=542668
Log:
Removed old site scripts.
Removed:
directory/project/releases/7/resources/generate_modules_index_xdoc.sh
directory/project/releases/7/resources/pomartifactId.sh
directory/project/releases/7/resources/pomdesc.sh
directory
Please hold back all commits on trunks until both these releases have
been completed. Should be done shortly after testing final jars.
Thanks,
Alex
Hi,2005/10/31, Brett Porter [EMAIL PROTECTED]:
I just want to ensure releases are m2-compatible. This just meansreleasing using Maven 1.1 beta 2, or Maven 1.0.2 with Maven ArtifactPlugin 1.5.2 installed. These ensure that the POM deployed resolvesany inheritance and expressions (not a big problem
I just want to ensure releases are m2-compatible. This just means
releasing using Maven 1.1 beta 2, or Maven 1.0.2 with Maven Artifact
Plugin 1.5.2 installed. These ensure that the POM deployed resolves
any inheritance and expressions (not a big problem in directory, but
worth noting).
Cheers
101 - 144 of 144 matches
Mail list logo
