cblib 2.0.2 wrapping
Key: FELIX-205
URL: https://issues.apache.org/jira/browse/FELIX-205
Project: Felix
Issue Type: New Feature
Components: Felix Commons
Reporter: Felix Meschberger
Prio
[
https://issues.apache.org/jira/browse/FELIX-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-205:
Attachment: pom.xml
Same attachement with ASF grant this time (forgot to check the first tim
[
https://issues.apache.org/jira/browse/FELIX-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-205:
Attachment: pom.xml
POM to include the complete cglib-full jar contents with dynamic imports
commons-beanutils 1.7.0 wrapping
Key: FELIX-206
URL: https://issues.apache.org/jira/browse/FELIX-206
Project: Felix
Issue Type: New Feature
Components: Felix Commons
Reporter: Felix Mesc
[
https://issues.apache.org/jira/browse/FELIX-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-207:
Attachment: pom.xml
> commons-codec 1.2 wrapping
> --
>
>
[
https://issues.apache.org/jira/browse/FELIX-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-206:
Attachment: pom.xml
> commons-beanutils 1.7.0 wrapping
>
>
commons-codec 1.2 wrapping
--
Key: FELIX-207
URL: https://issues.apache.org/jira/browse/FELIX-207
Project: Felix
Issue Type: New Feature
Components: Felix Commons
Reporter: Felix Meschberger
[
https://issues.apache.org/jira/browse/FELIX-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-208:
Priority: Minor (was: Major)
> commons-configuration 1.3 wrapping
> ---
commons-configuration 1.3 wrapping
--
Key: FELIX-208
URL: https://issues.apache.org/jira/browse/FELIX-208
Project: Felix
Issue Type: New Feature
Components: Felix Commons
Reporter: Felix
[
https://issues.apache.org/jira/browse/FELIX-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-208:
Attachment: pom.xml
POM including Commons Configuration with dynamic imports for XML and DB
commons-digester 1.8 wrapping
-
Key: FELIX-209
URL: https://issues.apache.org/jira/browse/FELIX-209
Project: Felix
Issue Type: New Feature
Components: Felix Commons
Reporter: Felix Meschberge
[
https://issues.apache.org/jira/browse/FELIX-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-209:
Attachment: pom.xml
Dynamic import for commons.logging.impl package, which seems to only be
commons-el 1.0 wrapping
---
Key: FELIX-210
URL: https://issues.apache.org/jira/browse/FELIX-210
Project: Felix
Issue Type: New Feature
Components: Felix Commons
Reporter: Felix Meschberger
commons-fileupload 1.1.1 wrapping
-
Key: FELIX-211
URL: https://issues.apache.org/jira/browse/FELIX-211
Project: Felix
Issue Type: New Feature
Components: Felix Commons
Reporter: Felix Me
[
https://issues.apache.org/jira/browse/FELIX-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-210:
Attachment: pom.xml
> commons-el 1.0 wrapping
> ---
>
>
[
https://issues.apache.org/jira/browse/FELIX-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-211:
Attachment: pom.xml
POM with dynamic import for javax.portlet package, which may or may not
commons-httpclient 3.0.1 wrapping
-
Key: FELIX-212
URL: https://issues.apache.org/jira/browse/FELIX-212
Project: Felix
Issue Type: New Feature
Components: Felix Commons
Reporter: Felix Me
[
https://issues.apache.org/jira/browse/FELIX-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-212:
Priority: Minor (was: Major)
> commons-httpclient 3.0.1 wrapping
>
[
https://issues.apache.org/jira/browse/FELIX-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-212:
Attachment: pom.xml
> commons-httpclient 3.0.1 wrapping
> -
commons-io 1.3 wrapping
---
Key: FELIX-213
URL: https://issues.apache.org/jira/browse/FELIX-213
Project: Felix
Issue Type: New Feature
Components: Felix Commons
Reporter: Felix Meschberger
Create a
[
https://issues.apache.org/jira/browse/FELIX-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-181:
Attachment: pom.xml
How about doing 2.2 immediately ?
> commons-lang 2.1 wrapping
> ---
[
https://issues.apache.org/jira/browse/FELIX-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-213:
Attachment: pom.xml
> commons-io 1.3 wrapping
> ---
>
>
[
https://issues.apache.org/jira/browse/FELIX-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-213:
Priority: Minor (was: Major)
> commons-io 1.3 wrapping
> ---
>
>
Oops, I just noticed that I replied to the wrong email message.
I found that I can use my maven repository as my OBR by adding
repository.xml. I copied http://oscar-osgi.sf.net/obr2/repository.xml
to ~/.m2/repository, then manually edited it to match the bundles that
I've installed in my mave
Tim Moloney wrote:
Oops, I just noticed that I replied to the wrong email message.
I found that I can use my maven repository as my OBR by adding
repository.xml. I copied http://oscar-osgi.sf.net/obr2/repository.xml
to ~/.m2/repository, then manually edited it to match the bundles that
I've
Required properties inside the Configuration Handler
Key: FELIX-214
URL: https://issues.apache.org/jira/browse/FELIX-214
Project: Felix
Issue Type: Bug
Components: iPOJO
Hi,
On 2/10/07, Steven E. Harris <[EMAIL PROTECTED]> wrote:
Felix Meschberger <[EMAIL PROTECTED]> writes:
> In fact we do exactly this at our place: Define bundle sets and have
> a management agent control the lifecycle
What defines a set of bundles? Is it their symbolic names?
Actually, t
[
https://issues.apache.org/jira/browse/FELIX-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier updated FELIX-214:
Attachment: required_props.patch
The patch need to be applied on the iPOJO core project.
It
[
https://issues.apache.org/jira/browse/FELIX-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-214.
-
Resolution: Fixed
Assignee: Richard S. Hall
I applied this patch.
> Required properties ins
[
https://issues.apache.org/jira/browse/FELIX-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-198.
-
Resolution: Fixed
Assignee: Richard S. Hall
I applied this patch and updated the build.xml t
I have applied a patch from John Conlon to create a new, single pom.xml
file that separates the Felix subprojects into profiles according to
their packaging type. This was necessary to avoid a bug in Maven which
appears when a project has more than one type of packaging plugins
(Felix has three
Hi everybody,
I asked the same question some time ago and was redirected to the bindex tool,
which you can download from the OSGi site. This allows you to statically
generate a remository.xml file that reflects the contents of a repository. It
works on maven repositories or caches. In my team,
"Richard S. Hall" <[EMAIL PROTECTED]> writes:
>* "mvn -Dpackaging=bundle clean install" - this builds all
> subprojects that use the new bundle plugin.
After updating to the latest along the Subversion trunk, I see this:
$ mvn -Dpackaging=bundle clean install
[INFO] Scanning for project
From what Peter says, it doesn't sound like this is easily possible:
This is not possible ... The bnd file == the manifest. You can't have the
definition in two places. So or you use the PDE where the manifest describes
your classpath (together with Eclipse magic), and then no bnd. Or you us
Felix Meschberger <[EMAIL PROTECTED]> writes:
> Actually, the bundle set descriptor is a bundle itself, which has a
> special manifest header naming other bundles (or resources in OBR
> speak) to be managed. The reference is by bundle symbolic name and a
> version range.
This is interesting. The
"Richard S. Hall" <[EMAIL PROTECTED]> writes:
> And, in general, it is not a good idea to make expedient decisions
> because then it is hard to back away from them later.
I understand.
> The resource gives you the symbolic name and version, which uniquely
> identifies the bundle.
Yes, though un
GERODOLLE Anne RD-MAPS-GRE wrote:
Hi everybody,
I asked the same question some time ago and was redirected to the bindex tool, which you can download from the OSGi site. This allows you to statically generate a remository.xml file that reflects the contents of a repository. It works on maven rep
Actually I have almost get it to work, the manifest just seems not to
be right yet.
Latest code of my branch of the bundle plugin is at
http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-bundle-plugin/
if you want to give it a try.
On 2/12/07, Richard S. Hall <[EMAIL PROTECTED]> wrote:
Strange. I just did it and it works for me...
mvn -Dpackaging=bundle clean install
...
[INFO] BUILD SUCCESSFUL
-> richard
Steven E. Harris wrote:
"Richard S. Hall" <[EMAIL PROTECTED]> writes:
* "mvn -Dpackaging=bundle clean install" - this builds all
subprojects that use
Steven E. Harris wrote:
"Richard S. Hall" <[EMAIL PROTECTED]> writes:
And, in general, it is not a good idea to make expedient decisions
because then it is hard to back away from them later.
I understand.
The resource gives you the symbolic name and version, which uniquely
identi
"Richard S. Hall" <[EMAIL PROTECTED]> writes:
> Strange. I just did it and it works for me...
This is where Maven becomes annoying. It's hard to figure out what
could be wrong here. Maven's equivalent to Windows's "Have you tried
rebooting?" is "Have you tried removing your local repository?" I'l
Steven E. Harris wrote:
"Richard S. Hall" <[EMAIL PROTECTED]> writes:
Strange. I just did it and it works for me...
This is where Maven becomes annoying. It's hard to figure out what
could be wrong here. Maven's equivalent to Windows's "Have you tried
rebooting?" is "Have you tried re
"Richard S. Hall" <[EMAIL PROTECTED]> writes:
> Although this sounds like the "something spurious has happened so
> maybe you want to try again later" Maven issue. :-)
Wow, I hope so. I just removed my local repository and tried again,
with the same result. But note that I'm able to compile other
"Steven E. Harris" <[EMAIL PROTECTED]> writes:
> This may be related to the "repository" elements not specifying
> whether each repository offers snapshots or releases (I just tried
> adding these specifications, but the problem persists)
Adding the following elements to the pluginRepository elem
[
https://issues.apache.org/jira/browse/FELIX-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls reassigned FELIX-30:
---
Assignee: Karl Pauls
> Implement extension bundles
> ---
>
> Ke
[
https://issues.apache.org/jira/browse/FELIX-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472474
]
Karl Pauls commented on FELIX-22:
-
I removed the support for now. I will provided it as an extension bundle soon.
> Im
[
https://issues.apache.org/jira/browse/FELIX-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472476
]
Karl Pauls commented on FELIX-30:
-
As of Revision 506755 the extension:=framework part of the spec is implemented
with
Steven E. Harris wrote:
"Steven E. Harris" <[EMAIL PROTECTED]> writes:
This may be related to the "repository" elements not specifying
whether each repository offers snapshots or releases (I just tried
adding these specifications, but the problem persists)
Adding the following element
On 2/12/07, Steven E. Harris <[EMAIL PROTECTED]> wrote:
Felix Meschberger <[EMAIL PROTECTED]> writes:
> Actually, the bundle set descriptor is a bundle itself, which has a
> special manifest header naming other bundles (or resources in OBR
> speak) to be managed. The reference is by bundle symb
49 matches
Mail list logo
