commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Mietz Egli (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CHAIN-48) OSGi bundle without web framework dependencies
Date Fri, 29 May 2009 19:10:45 GMT

     [ https://issues.apache.org/jira/browse/CHAIN-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul Mietz Egli updated CHAIN-48:
---------------------------------

    Description: 
Thanks for providing the OSGi manifest for commons-chain!  It would be nice for those of us
that aren't using chain with a web framework to split the library into two bundles, one for
the base functionality and another which adds all of the web functionality.  I don't want
Faces, EL, JSTL, and all of that just to use Chain programatically.  Maybe you could publish
a commons-chain-base bundle without the web dependencies?

As a workaround, I modified the POM to exclude the web classes by adding the following complier
plugin config:
{code:xml}
          <plugin>
            <artifactId>maven-compiler-plugin</artifactId>
            <configuration>
              <excludes>
                <exclude>**/web/**</exclude>
              </excludes>
              <testExcludes>
                <exclude>**/web/**</exclude>
                <exclude>**/ContextBaseTestCase.java</exclude>
                <exclude>**/TestContextTestCase.java</exclude>
              </testExcludes>
            </configuration>
          </plugin>
{code}

  was:
Thanks for providing the OSGi manifest for commons-chain!  It would be nice for those of us
that aren't using chain with a web framework to split the library into two bundles, one for
the base functionality and another which adds all of the web functionality.  I don't want
Faces, EL, JSTL, and all of that just to use Chain programatically.  Maybe you could publish
a commons-chain-base bundle without the web dependencies?

As a workaround, I modified the POM to exclude the web classes by adding the following complier
plugin config:

          <plugin>
            <artifactId>maven-compiler-plugin</artifactId>
            <configuration>
              <excludes>
                <exclude>**/web/**</exclude>
              </excludes>
              <testExcludes>
                <exclude>**/web/**</exclude>
                <exclude>**/ContextBaseTestCase.java</exclude>
                <exclude>**/TestContextTestCase.java</exclude>
              </testExcludes>
            </configuration>
          </plugin>



> OSGi bundle without web framework dependencies
> ----------------------------------------------
>
>                 Key: CHAIN-48
>                 URL: https://issues.apache.org/jira/browse/CHAIN-48
>             Project: Commons Chain
>          Issue Type: Wish
>    Affects Versions: 1.2
>            Reporter: Paul Mietz Egli
>            Priority: Minor
>
> Thanks for providing the OSGi manifest for commons-chain!  It would be nice for those
of us that aren't using chain with a web framework to split the library into two bundles,
one for the base functionality and another which adds all of the web functionality.  I don't
want Faces, EL, JSTL, and all of that just to use Chain programatically.  Maybe you could
publish a commons-chain-base bundle without the web dependencies?
> As a workaround, I modified the POM to exclude the web classes by adding the following
complier plugin config:
> {code:xml}
>           <plugin>
>             <artifactId>maven-compiler-plugin</artifactId>
>             <configuration>
>               <excludes>
>                 <exclude>**/web/**</exclude>
>               </excludes>
>               <testExcludes>
>                 <exclude>**/web/**</exclude>
>                 <exclude>**/ContextBaseTestCase.java</exclude>
>                 <exclude>**/TestContextTestCase.java</exclude>
>               </testExcludes>
>             </configuration>
>           </plugin>
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message