Hi,
Am Montag, den 06.08.2007, 09:15 -0700 schrieb Steven E. Harris:
> Carsten Ziegeler <[EMAIL PROTECTED]> writes:
>
> > And add the javadoc tags to your source code, and everything else is
> > done by the plugin.
>
> Is there a reason that you chose Javadoc tags over Java annotations?
Yes, w
+1
Regards and thanks for your hard work !
Felix
Am Montag, den 06.08.2007, 23:00 +0200 schrieb Karl Pauls:
> I would like to call a vote on the framework and main binaries in
> order to make them available via maven. The jar artifacts, the
> signature files, and MD5 message digests are available
[X] +1 Approve the Felix 1.0.0 framework and main binary releases.
Clement
+1
On 07/08/07, Karl Pauls <[EMAIL PROTECTED]> wrote:
> I would like to call a vote on the framework and main binaries in
> order to make them available via maven. The jar artifacts, the
> signature files, and MD5 message digests are available here:
>
>
> http://people.apache.org/~pauls/felix-1.0.
On Tuesday 07 August 2007 05:47, Karl Pauls wrote:
> I'm not sure I really like the idea that we create all those artifacts
> of other projects.
I am sort of -0 on this topic. And that is why Pax Construct (www.ops4j.org)
exists, so it is easy to create and maintain those wrappers "at home" and
On Tuesday 07 August 2007 05:12, Karl Pauls wrote:
> On this subject, would you mind if I replace your signature with our
> release key signature?
The KEYS file will contain multiple keys over time, as release manager will
both be varying over time and commonly over different parts of the project
On Tuesday 07 August 2007 05:00, Karl Pauls wrote:
> I would like to call a vote on the framework and main binaries in
> order to make them available via maven. The jar artifacts, the
> signature files, and MD5 message digests are available here:
[x] +1 Approve the Felix 1.0.0 framework and main b
On Aug 6, 2007, at 23:47 , Karl Pauls wrote:
It might just be me so fell free to ignore this if nobody else has a
strange felling about providing and maintaining all those artifacts...
I agree the most natural place for maintaining those artifacts, which
basically just add meta-data to the e
On 7/24/07, Richard S. Hall <[EMAIL PROTECTED]> wrote:
> Regarding releasing Commons bundles, I share Marcel's concern that we
> need to have a controlled release process so that we can have some sort
> of quality assurance about what we are releasing.
Yes - my thinking exactly.
> However, I do a
On 7/26/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Niclas Hedhman wrote:
> > On Tuesday 24 July 2007 20:53, Carsten Ziegeler wrote:
> >> Now, I have the hope that releasing is just a matter of invoking maven
> >> (with the correct arguments).
> >
> > First step is just the production of a pa
On 7/24/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I updated our commons project, main changes are:
> - parent pom is now in "pom" (similar to our root pom)
> - convenience pom under /commons to build the whole tree
> - Only released artifacts are used (maven-bundle-plugin:1.0.0,
> r
> I would like to call a vote on the framework and main binaries in
> order to make them available via maven. The jar artifacts, the
> signature files, and MD5 message digests are available here:
>
>
> http://people.apache.org/~pauls/felix-1.0.0-binary.html
>
>
> Please vote to approve these releas
+1
On 7/27/07, Karl Pauls <[EMAIL PROTECTED]> wrote:
> On 7/24/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> > Marcel Offermans wrote:
> > >
> > > I agree that it's a lot of work for one person, and dividing the
> > > responsibility might be a good idea, Felix is a complicated project that
> > > c
On 7/29/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Marcel Offermans schrieb:
> > On Jul 29, 2007, at 19:01 , Carsten Ziegeler wrote:
> >
> >> Carsten Ziegeler wrote:
> >>> I'll put the artifacts in the maven repo over the weekend.
> >>>
> >> Hmm, it seems that I did not think this through :(
> putting our releases up to the maven repository was a little bit work,
> as I had to create the correct directory structure by hand and (more
> important) had to extract the pom files for the various artifacts,
> create md5s and sign them.
On this subject, would you mind if I replace your signat
> The release plugin now supports a staging area. One can take a look at
> CXF for example (or maybe the naven site).
Interesting. I'll definitely have a look at that!
regards,
Karl
> On 7/21/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> > On Saturday 21 July 2007 01:34, Carsten Ziegeler wrot
Hopefully we can make the artifacts available by the end of the week.
regards,
Karl
On 8/5/07, Herko ter Horst <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> I was wondering if the Felix framework jar is available in a public
> Maven repository somewhere.
>
> The main repo (http://repo1.maven.org/mav
I would like to call a vote on the framework and main binaries in
order to make them available via maven. The jar artifacts, the
signature files, and MD5 message digests are available here:
http://people.apache.org/~pauls/felix-1.0.0-binary.html
Please vote to approve these release archives:
[
Carsten Ziegeler <[EMAIL PROTECTED]> writes:
> And add the javadoc tags to your source code, and everything else is
> done by the plugin.
Is there a reason that you chose Javadoc tags over Java annotations?
> WDYT?
There are some facets specified in these tags that I'd be reluctant to
include i
[
https://issues.apache.org/jira/browse/FELIX-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517927
]
Stuart McCulloch commented on FELIX-308:
BTW, if you want to add a dependency to your pom (ie. for embedding p
[
https://issues.apache.org/jira/browse/FELIX-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch updated FELIX-308:
---
Attachment: FELIX_308_EMBED_SUPPORT_20070806.txt
Updated patch: FELIX_308_EMBED_SUPPORT_200708
[
https://issues.apache.org/jira/browse/FELIX-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch updated FELIX-308:
---
Description:
The following is a proposal for how to support embedding dependency JAR files
in
[
https://issues.apache.org/jira/browse/FELIX-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517861
]
Felix Meschberger commented on FELIX-334:
-
The problem, as correctly stated, is that the updated configuration
[
https://issues.apache.org/jira/browse/FELIX-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed FELIX-334.
---
Resolution: Fixed
Fix Version/s: 1.0.0
After deploying a new snapshot of the ConfigAdmi
Hi,
Felix and myself (well, basically Felix has done all the work and I did
just some minor enhancements) have put a new maven plugin into my sandbox.
The scr plugin generates the configuration file for the declarative
services based on javadoc tags in the source code. It generates the
component
[
https://issues.apache.org/jira/browse/FELIX-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned FELIX-334:
---
Assignee: Felix Meschberger
> Missing callbacks for Configuration plugins
> --
Missing callbacks for Configuration plugins
---
Key: FELIX-334
URL: https://issues.apache.org/jira/browse/FELIX-334
Project: Felix
Issue Type: Bug
Components: Configuration Admin
28 matches
Mail list logo
