directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn McKinney <smckin...@apache.org>
Subject Re: [Fortress] fortress-core release
Date Fri, 03 Apr 2015 14:44:16 GMT
Hello, this is my first release with apache directory project so please forgive the naive questions….


> On Apr 3, 2015, at 6:46 AM, Emmanuel Lécharny <elecharny@gmail.com> wrote:
> 
> I have cleaned up the fortress-core pom to be able to cut a first
> release. The idea is to not depend on a parent pom at the moment, but
> release the four different projects (with enmasse, realm and commander)
> separately. We will most certainly regroup all of them later, but that
> requires a new git repo.
> 

OK

> On Apr 3, 2015, at 6:46 AM, Emmanuel Lécharny <elecharny@gmail.com> wrote:
> 
> The release will only be a source release (ie, we won't generate a
> binary package containing all the needed jars). As this is a library, it
> makes sense, as most of our users will use Maven (or a flavor of maven)
> to pull the jars.

Agreed.  Assuming by this you mean we will still release (upload to maven central repo) the
targets of the maven install operation. 


> On Apr 3, 2015, at 6:46 AM, Emmanuel Lécharny <elecharny@gmail.com> wrote:
> 
> For commander, it's a bit more complex, and I'm waiting for some input
> to decide how to release it, as we wnt to produce a war.
> 
> Thanks for testing the first release as soon as t will be out (later today).

I struggle with the idea of publishing a .war for commander.  Before this app may be deployed
(correctly), it requires configuration settings for a particular ldap host server.  In this
scenario, a user would have to hand edit a config file and poke it back into the .war before
it would work.  Not a very good practice IMO.  I’ll need to think about this and come up
with a solution.

> On Apr 3, 2015, at 6:46 AM, Emmanuel Lécharny <elecharny@gmail.com> wrote:
> 
> Thanks for testing the first release as soon as t will be out (later today).

Tried to build and received an error pulling down directory api-all M29.   Understand this
has *just* been released so this is probably just a timing issue.

One problem I can see is the maven install isn’t publishing the javadoc artifacts to the
local .m2 repo, though it can be found under target.  Not a showstopper, just something to
figure out.

Thanks,

Shawn
Mime
View raw message